-
Notifications
You must be signed in to change notification settings - Fork 13
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
Migrate to eslint flat config #830
Comments
Thanks! Need to check whether all the configs that eslint-config-hardcore extends from support the new format. |
Sorry, it seems like that's a duplicate of #726 Good article, by the way. I really recommend that one. |
Now eslint 9.0 released |
@EvgenyOrekhov any update on this one |
@The-Code-Monkey I don't have the capacity to maintain both config formats, so I'll migrate to flat config as soon as TypeScript ESLint v8 gets released and Shopify/web-configs#425 gets fixed. Or maybe even remove Shopify plugin temporarily, if they take longer. |
Ok that's fine I was just curious, thanks for maintaining
…On Mon, 10 Jun 2024, 01:51 Evgeny Orekhov, ***@***.***> wrote:
@The-Code-Monkey <https://github.com/The-Code-Monkey> I don't have the
capacity to maintain both config formats, so I'll migrate to flat config as
soon as TypeScript ESLint v8 gets released and Shopify/web-configs#425
<Shopify/web-configs#425> gets fixed. Or maybe
even remove Shopify plugin temporarily, of they take longer.
—
Reply to this email directly, view it on GitHub
<#830 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHOFWX7BZVN4HDIAFOYU2RTZGT2BFAVCNFSM6AAAAAA6K7XC32VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNJWHE3DQMZQG4>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
TypeScript ESLint 8.0.0 has been released. Shopify/web-configs#425 isn't closed but they did migrate to flat config. |
Interested in this as well. It seems like all the barriers should have been removed now. I second the need for an example of this new format in the doc, seems pretty intricate to me. |
Hello! First of all, I want to express my appreciation for your fantastic project! It's great to see the effort and dedication put into it.
One aspect that I'd like to discuss is the configuration format used in eslint-config-hardcore. Currently, it employs a legacy configuration format that might not be as flexible and composable as the new format. This happens to be the main obstacle preventing me from using eslint-config-hardcore.
The ESLint Flat config is a significant improvement for the ecosystem, and it's encouraging to know that the transition from the legacy format is on the horizon. For more information about this exciting development, you can check out the following resources:
https://eslint.org/docs/latest/use/configure/configuration-files-new
https://eslint.org/blog/2023/10/flat-config-rollout-plans
https://www.raulmelo.me/en/blog/migration-eslint-to-flat-config
eslint/eslint#3458
eslint/eslint#10643
eslint/eslint#13481
ESLint v9 migration:
"enforceForClassMembers": true
option fromno-useless-computed-key
rule (it's the default in v9)The text was updated successfully, but these errors were encountered: