-
Notifications
You must be signed in to change notification settings - Fork 208
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
Support for ESLint's New Flat Configs #830
Comments
Happy to review a PR if someone wants to convert the existing RC to the new config style. |
Eslint has deprecated the use of config files that are not the new flat configs. |
Working on the flat config for the next release |
Thanks Tony :) Happy to test anything then. I've moved away from it for now, but I can make sure to come back and help look at it. |
#886 Gets pretty close but we will need to wait for Node 14/16 deprecation to bump ESlint versions. Might be able to do it without that package change. I'll take a better look as soon as I have time. |
When will we get this ? |
Hi. |
This currently prevents using |
Is this project still active? is there an alternative project that does something similar that works with eslint 9.x? |
@tonycoco , looks like NodeJS 14/16 are status = 'End-of-Life': https://github.com/nodejs/Release |
Available in newer versions of ESLint, and will be required in the future, there's a new configuration structure! You can find the context here: https://eslint.org/docs/latest/use/configure/configuration-files-new
While there does exist a utility (https://www.raulmelo.me/en/blog/migration-eslint-to-flat-config#official-utility-for-the-rescue) to convert between the two, it's a bit gross, and I didn't have much luck with it properly loading in the overrides.
We were using the https://github.com/google/gts#working-with-eslint aspect of this in a few of our repos! And I wound up essentially making my own using the same rules over in the new style.
Thanks for your time, and your support!
The text was updated successfully, but these errors were encountered: