Bug: npm init @eslint/config generates broken-by-default config file #18361
Unanswered
ChristopherJTrent
asked this question in
Q&A
Replies: 2 comments
-
Hi @ChristopherJTrent, can you try running |
Beta Was this translation helpful? Give feedback.
0 replies
-
So, that generates a valid config file, but installs ESLint 8 as a dependency for all of the available templates |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Environment
Node version: 21.6.2
npm version: 10.5.2
Local ESLint version: 9.0.0
Global ESLint version: 9.0.0
Operating System: Arch Linux
Node and npm installed using asdf v0.14.0
What parser are you using?
Default (Espree)
What did you do?
I ran
npm init @eslint/config
and followed the prompts to create a configuration fileWhat did you expect to happen?
I expected it to generate a valid eslint 9 configuration file
What actually happened?
it generated a non-eslint 9 compatible config file
Link to Minimal Reproducible Example
https://github.com/ChristopherJTrent/eslint_example
Participation
Additional comments
No response
Beta Was this translation helpful? Give feedback.
All reactions