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
Eslint init create-config creates a config that does not work with VSCode extension #107
Comments
For the time being, you'll need to still set `eslint.experimental.useFlatConfig": true' to enable the config file in VS Code. There is a prerelease version that will auto-detect flat config: We have a lot of documentation about how to use the new config system, start here: There's also this: Note: We do not maintain the VS Code ESLint plugin. For further help, you'll need to work with them: |
Steps to reproduce:
package.json
file withnpm init -y
npm init @eslint/config@latest
This package creates a config
eslint.config.mjs
. Here are some problems:The extension does not lint, nor higlight, nor fix
.js
files2. The option
"eslint.experimental.useFlatConfig": true,
in settings.json does help, but is it still experimental?3. It is impossible to load new configs/plugins in this file. For example, prettier:
npm i -D eslint-config-prettier
compat.extends("airbnb-base", 'prettier'),
and the new config does not work. Eslint still higlights formatting rules even after restarting eslint serverPlease, provide some info on how to use this new eslint config.
The text was updated successfully, but these errors were encountered: