-
-
Notifications
You must be signed in to change notification settings - Fork 65
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
Switch to Flat Config Format #1299
Comments
We'd love to do that but I don't yet have npm publish permission for eslint-config-standard or any package other than this one. |
Ah, gotcha. Thanks for the clarification. 🙂 |
Just out of curiosity, when you do get to that point, were you thinking of using the new cascade so eslint-config-standard would apply to JavaScript files and eslint-config-standard-with-typescript would apply to TypeScript files? Something like this? [
{
...eslintConfigStandard,
files: ["*.js", "*.jsx", "*.cjs", "*.msj"]
},
{
...eslintConfigStandardWithTypeScript,
files: ["*.ts", "*.tsx"]
}
] |
I'm thinking of leaving setting file patterns to the user. |
As a workaround : import { FlatCompat } from '@eslint/eslintrc'
const compat = new FlatCompat()
export default [
...compat.extends('standard-with-typescript'),
] See https://eslint.org/docs/latest/use/configure/migration-guide#using-eslintrc-configs-in-flat-config |
Note also that, related to this, this statement is out-of-date:
|
With #1498 this is right around the corner! |
How should I import eslint-config-love into eslint.config.js? This is file, I don't think writing
I used this workaround before
|
## [48.0.0](v47.0.0...v48.0.0) (2024-05-18) ### ⚠ BREAKING CHANGES * exports an ESLint flat config. ### Build system / dependencies * use semantic-release/commit-analyzer preset ([790b662](790b662)) ### Features * flat config ([a0571e7](a0571e7)), closes [#1299](#1299) [#1210](#1210) ### Testing * rm redundant parserOptions test ([0e49fea](0e49fea))
🎉 This issue has been resolved in version 48.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Are these packages no longer necessary? or do they still need to be installed as stated in the previous version?
If I remove them all it gives me this error and I had to reinstall eslint:
The new version still throw exception:
eslint.config.js
eslint-config-love/lib/index.js
|
@zN3utr4l eslint and typescript are now the only peerDeps. Since it seems obvious that all users would have them installed, the entire section was removed. Sorry. Could you, please use the discussions feature for support? I'd love to help you there. |
Commenting here in case it might help anyone landing here in the future. At the time of writing, if you encounter the |
I saw in this commit in eslint-config-standard that the repo has been switched over to the new ESLint flat config format. It'd be cool if this repo could be switched over as well. 🙂
The text was updated successfully, but these errors were encountered: