Skip to content

fix(plugins): parse name issue with invalid plugins #5770

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Merged
merged 1 commit into from
Feb 2, 2024

Conversation

NathanWalker
Copy link
Contributor

@NathanWalker NathanWalker commented Nov 2, 2023

PR Checklist

What is the current behavior?

If a plugin contains invalid data like the wrong name according to package.json, a 'path' from 'undefined' ambiguous error occurs.

What is the new behavior?

This will now print the name of the invalid package to allow one to resolve effectively.

Fixes/Implements/Closes #[Issue Number].

@cla-bot cla-bot bot added the cla: yes label Nov 2, 2023
@NathanWalker NathanWalker merged commit f826248 into main Feb 2, 2024
@NathanWalker NathanWalker deleted the fix/plugin-data-parse-issue branch February 2, 2024 02:58
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant