Open theoludwig opened 5 months ago
This might be handy for you as I had stumbled upon your config:
Also this comment is subject to change
no-new-symbol
deprecated and replaced by no-new-native-nonconstructorno-confusing-arrow
deprecated in ESLint v8.53.0no-mixed-operators
deprecated in ESLint v8.53.0quote-props
deprecated in ESLint v8.53.0Out of context of this issue, we might want to remove
{ "allowKeywords": true }
fordot-notation
because by default it is set to true, same forenforceForSwitchCase
option key insideuse-isnan
,newIsCap
option key insidenew-cap
,allowSamePrecedence
option key insideno-mixed-operators
Again out of context, we might want to add
enforceForJSX
to true inno-unused-expressions
Related issues:
Yesterday, I started migrating from v8.5.6 to v9.2.0 in another project, and it was a burden because of how much the Eslint's server, I guess, is no synced with the VSCode extension's version. I had to install the pre-release version, and yet I ran onto issues where .eslintrc
files couldn't be found because Eslint has switched to flat configs: eslint.config.js
, and this is where I realized that this wouldn't be possible, at least for for now, because a lot of plugins that currently use do not support the latest version of Eslint.
I think we just have to wait for merge PRs.
Reference: https://eslint.org/blog/2024/04/eslint-v9.0.0-released/