Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

No error stack when plugin module cannot be found #1044

Closed
JoshuaKGoldberg opened this issue Oct 2, 2023 · 1 comment
Closed

No error stack when plugin module cannot be found #1044

JoshuaKGoldberg opened this issue Oct 2, 2023 · 1 comment

Comments

@JoshuaKGoldberg
Copy link

Spinning off of #1043: if a plugin name cannot be resolved, the thrown error doesn't include an explanation of why or which paths were attempted. I think it might be useful to include that information. Do you think logging the caught errors in lib/plugin/factory's load sounds reasonable?

const load = async pluginName => {

@webpro webpro closed this as completed in 138277a Jul 8, 2024
@webpro
Copy link
Collaborator

webpro commented Jul 8, 2024

🚀 This issue has been resolved in v17.4.2. See Release 17.4.2 for release notes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants