-
Notifications
You must be signed in to change notification settings - Fork 69
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
Debugging "Failed to load config" #235
Comments
Thanks for reporting. I made #87 quite some time ago since I had trouble fixing issues myself. It would be great to get some help implementing something like this. |
Have the same issue on eslint P.S. |
Huh, I don't have a file of that name anywhere on my filesystem. I haven't encountered it again since I filed this, though. I still think more informative output would be helpful (though I guess it depends whether |
this solved it for me too. although it would be interesting to know why it fixed the issue. |
Had a similar issue with a Next.js 13 project where it would fail to load the config from eslint-config-next. Regular eslint worked fine, but for eslint_d running |
This is probably obsolete with the new major |
I've had several instances lately where
eslint
works fine, buteslint_d
reportsFailed to load config "whatever" to extend from.
These are shared configs that are loaded as npm modules. I hate writing a bad bug report, and I don't really have enough info to report an issue about the specifics, so... I'm reporting an issue about not being able to get enough info about the specifics. :-)Is there anywhere to get additional details about this kind of path resolution failure?
$ eslint_d src Error: Failed to load config "erich" to extend from. Referenced from: /home/erich/tmp/sandbox/.eslintrc.js
The references config is e.g.:
The referenced config is present in
node_modules/eslint-config-erich
(https://www.npmjs.com/package/eslint-config-erich). This has happened with others, though. E.g. one of my projects at work references https://www.npmjs.com/package/eslint-plugin-etc as a plugin, and the same issue occurs.The text was updated successfully, but these errors were encountered: