feat: migrate playground to ESLint v10 #853
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for new-eslint ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for ja-eslint ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for hi-eslint ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for zh-hans-eslint ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for pt-br-eslint ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for fr-eslint ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for de-eslint ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for es-eslint ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
mdjermanovic
reviewed
Dec 1, 2025
3 tasks
1 task
1 task
Pixel998
commented
Dec 20, 2025
| }, | ||
| "dependencies": { | ||
| "eslint": "latest" | ||
| "eslint": "10.0.0-beta.0" |
Contributor
Author
There was a problem hiding this comment.
Reminder to revert this when eslint v10 is released, and to not merge this PR before this is updated.
Contributor
Author
|
This should be ready for review. |
mdjermanovic
reviewed
Jan 5, 2026
mdjermanovic
reviewed
Jan 5, 2026
Hardanish-Singh
approved these changes
Jan 7, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Prerequisites checklist
What is the purpose of this pull request?
This PR migrates the Playground to be compatible with ESLint v10. The main issue is that ESLint v10 removes the
Linter#getRules()API, which the Playground currently uses to get core rules metadata. Additionally,@typescript-eslint/scope-manager(which is used by@typescript-eslint/parser) doesn't yet implement the new interface required by ESLint v10, causing ESLint to crash when TypeScript code is analyzed in the Playground.What changes did you make? (Give an overview)
rules_meta.jsoncontaining metadata for all ESLint core rules, and modified the Playground to load rule metadata from the generated JSON file instead of usingLinter#getRules().@typescript-eslint/parser(copied from the main repository) that adds the missingaddGlobals()method to the scope manager.Related Issues
Fixes #854
Is there anything you'd like reviewers to focus on?