-
Notifications
You must be signed in to change notification settings - Fork 798
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
Update to eslint 9 #40555
Update to eslint 9 #40555
Conversation
Apparently leading slashes are no longer allowed.
Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.
Interested in more tips and information?
|
Thank you for your PR! When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:
This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖 The e2e test report can be found here. Please note that it can take a few minutes after the e2e tests checks are complete for the report to be available. Follow this PR Review Process:
Still unsure? Reach out in #jetpack-developers for guidance! Beta plugin:
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. Jetpack plugin: The Jetpack plugin has different release cadences depending on the platform:
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. Debug Helper plugin:
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. Backup plugin:
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. Boost plugin:
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. Search plugin:
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. Social plugin:
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. Starter Plugin plugin:
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. Protect plugin:
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. Videopress plugin:
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. Super Cache plugin:
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. Inspect plugin:
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. Wpcomsh plugin:
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. Automattic For agencies client plugin:
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. Classic Theme helper plugin plugin:
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. |
About the only thing left here that might be split out into a separate PR is part of b2e80ec, but that'd leave us with inconsistent docs and it's not that much in there. I did try to divide things up into logical chunks for the initial set of commits, in case that helps. |
Much appreciated! |
While we are here, can we please not require redundant JSDoc types in TypeScript files like Gutenberg does? |
Seems like something for a followup PR to me. Most of the config changes in this PR are about bringing things closer together, like using most of our base config in P.S. If you do that, you may want to additionally disable |
Alright, I'll try to create a follow up PR once this one is shipped. |
Proposed changes:
Eslint 9 brings a new config format, which means this PR also rewrites all the eslint configs. I took the opportunity to clean them up (although a good bit of that wound up in earlier PRs), and added code to fetch the textdomain from composer.json and whether the project uses React from package.json so we don't need to have so many boilerplate configs that just set a textdomain or enable React rules.
Other information:
Jetpack product discussion
Draft announcement: pdWQjU-14g-p2
Does this pull request change what data or activity we track or use?
None
Testing instructions:
eslint.config.mjs
.