ESLint v9.0
eslint.org
ESLint v9.0
1–10 of 49 posts
Re: ESLint v9.0
#2I tried to migrate a few nights ago but gave up for now as it was too many changes. I will give it another go this week on a full stomach.
Re: ESLint v9.0
#3I tried to migrate a few nights ago but gave up for now as it was too many changes. I will give it another go this week on a full stomach.
Every upgrade of eslint is nightmare so nothing unusual
Re: ESLint v9.0
#4Loving the fact that their flat config compatibility package has 83% the number of weekly downloads compared to their main package.
It was pretty obvious years ago that eslint messed up how package names are referenced in configs, and how they're resolved. Did it really require such a big change that affects the whole ecosystem? Microsoft seemed to have a pretty good solution with https://www.npmjs.com/package/@rushstack/eslint-patch
Re: ESLint v9.0
#5I tried to migrate a few nights ago but gave up for now as it was too many changes. I will give it another go this week on a full stomach.
So much of it is completely unnecessary breaking changes too. A good example is the config file, out of the box they no longer support using `.eslintrc.*` (you can still get this behavior back with a config flag), you're now expected to use `eslint.config.js` instead. So in short, they're just making every single project out there that relies on ESLint go and either add a flag or rename one file — for what?
Re: ESLint v9.0
#6I tried to migrate a few nights ago but gave up for now as it was too many changes. I will give it another go this week on a full stomach.
So much of it is completely unnecessary breaking changes too. A good example is the config file, out of the box they no longer support using `.eslintrc.*` (you can still get this behavior back with a config flag), you're now expected to use `eslint.config.js` instead. So in short, they're just making every single project out there that relies on ESLint go and either add a flag or rename one file — for what?
Could it be a gradual move towards standardizing on js config files? Perhaps version 9 will only parse js configs, and this is a step towards that.
Edit: Here’s some info about the gradual migration to flat config and deprecation of eslintrc: https://eslint.org/blog/2023/10/flat-config-rollout-plans/
It seems like it’s been well thought out.
Re: ESLint v9.0
#7[deleted]
Re: ESLint v9.0
#8any ES linter written in rust?
Re: ESLint v9.0
#9any ES linter written in rust?
Check biome or oxlint.
I don't think any of them support all the rules of eslint
Re: ESLint v9.0
#10any ES linter written in rust?
Check biome or oxlint. I don't think any of them support all the rules of eslint
I've been using biome since it was called rome. It's an excellent formatter / linter and reduces the configuration down to a single npm install and a single json file.
I highly recommend people try it out and ditch the configuration nightmare that is eslint.