-
-
Notifications
You must be signed in to change notification settings - Fork 12
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
Error: Failed to load config "standard" to extend from. #27
Comments
ping? I'm also seeing this, with a similar setup. The |
Apparently the error comes from the fact that ESLint v6 now demands that all plugins are installed locally as seen here and here. Replacing the |
@ManuelFte @indigoviolet In the meantime of that wrong configuration of eslint, I could resolve fallback of version
That's all Extra tip: I was having some problems with paths, etc.. so I ended to add a script to my
and finally, just be sure that you are importing the rest of configurations that are described here That's it, then It's working as I expected. :) |
This is still an issue, we should look into fixing this with the eslint @ 7 upgrade. I think eslint @ 7 is supposed to fix this, cc @LinusU who's got the eslint7 PR. |
Still an issue for me:
|
I think resolve plugins relative to is supposed to help with this maybe :( |
@Jero786 standardx 3.0.0 uses ES 2018, so you still have to change the version numbers as I had mentioned in order to use at least ES 2019. Hopefully this issue is fixed soon because ES 2020 has just been released. |
I tried with another a new project and am hitting the same problem. So is it the case that no one is using latest standardx to add typescript support to standard? |
I used standardx 3.0.0 because reasons :( |
I got this issue today and solved it by installing the following packages: npm install eslint --save-dev |
This worked for me, but I didn't need all these packages (it's dependent on your setup). Running |
…ard's typescript support is wonky See standard/standardx#27
…ard's typescript support is wonky See standard/standardx#27
In my case, it was resolved by removing all these packages and restart VSCode. |
Is this still an issue in the latest version of |
Let me try. |
Yes. |
In
Instead of Maybe giving it a fileName for a json file with |
I tried that locally and it doesn't help. |
Thanks for checking, @Raynos. I can't reproduce this issue on my machine. A PR that fixes this would be really helpful to get this resolved. |
Also ended up installing thse packages that made it work (although I don't need most of them - in theory)
|
Any suggestion how to fix this without installing all those |
I am running out of ideas so I've created a testcase to reproduce it.
|
Hello! 👋 I was able to get something working that resolves this issue in PR #38. Sanity checks by interested folks here would be cool! |
Any news on this? Is it at all possible to have a working global installation of standardx? |
In my case, using PR #38 and removing the setting |
Any news on it? I just installed 7.0.0 and I'm getting: npx standardx Error: Failed to load config "standard" to extend from. |
What version of this package are you using?
5.0.0 (standard 14.3.1)
What operating system, Node.js, and npm version?
Manjaro KDE, Node v13.5.0, npm v6.13.4
What happened?
sudo npm install standardx --global
standardx --fix
in my local project folder.What did you expect to happen?
To run the autofixer.
Are you willing to submit a pull request to fix this bug?
I'm not familiar with the code, so I don't think I could.
The text was updated successfully, but these errors were encountered: