-
Notifications
You must be signed in to change notification settings - Fork 10.3k
Upgrade eslint
to version 9.0.0
#17928
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
Comments
Let's make it a tracking issue then :D Plugins
|
This is a major version bump, but the changelog at https://github.com/sindresorhus/eslint-plugin-unicorn/releases/tag/v53.0.0 doesn't indicate any breaking changes that should impact us. Most notably it contains support for ESLint 9, which brings us a step closer towards mozilla#17928.
In commit d7f2bc0 |
If you haven't already seen https://eslint.org/blog/2024/05/eslint-compatibility-utilities/, it might be useful for this. It provides wrappers to run ESLint 8 plugins in ESLint 9. |
I can comment for eslint-plugin-no-unsanitized: It's planned but blocked on dependencies (heh) |
|
In commit c77dbe0 |
In PR #18571 the idea came up of trying to remove We should check if this is possible since it would unblock the |
In commit be93d53 |
|
In commit ae13b4a |
Note that the new version of `eslint-plugin-import` contains support for ESLint 9. Fixes a part of mozilla#17928.
Note that the new version of `eslint-plugin-import` contains support for ESLint 9. Moreover, the new version of Babel removed the leading space for import comments, so we update the corresponding test expectation to match this. Fixes a part of mozilla#17928.
Note that the new version of `eslint-plugin-import` contains support for ESLint 9. Moreover, the new version of Babel removed the leading space for import comments (see babel/babel#16780), so we update the corresponding test expectation to match this. Fixes a part of mozilla#17928.
Note that the new version of `eslint-plugin-import` contains support for ESLint 9. Moreover, the new version of Babel removed the leading space for import comments (see babel/babel#16780), so we update the corresponding test expectation to match this. Fixes a part of mozilla#17928.
In commit 78bf528 |
In the PRs above we removed obsolete plugins and replaced |
It seems like now just bumping the version in package.json works, but I haven't had time to test deeply. |
This is unblocked now that all dependencies have been updated and the flat configuration format (compatible with ESLint 8 and 9) was introduced first. The following deprecation warnings during `npm install` are resolved by this upgrade: ``` npm warn deprecated @humanwhocodes/[email protected]: Use @eslint/config-array instead npm warn deprecated @humanwhocodes/[email protected]: Use @eslint/object-schema instead npm warn deprecated [email protected]: This version is no longer supported. Please see https://eslint.org/version-support for other options. ``` Note that according to https://eslint.org/version-support ESLint 8 is officially EOL now, and ESLint 9 has been released for over seven months and is the only officially supported version. Fixes mozilla#17928.
We should upgrade to ESLint 9 now that it's officially released. The changelog, including the breaking changes that should be audited, can be found at https://github.com/eslint/eslint/releases/tag/v9.0.0. Note that this upgrade is currently blocked on the ESLint plugins that we use indicating support for ESLint 9 in their
package.json
ranges first, so this is mostly a tracking issue at the moment.The text was updated successfully, but these errors were encountered: