docs: create ESLint 10 compatibility tracking document#271
Closed
docs: create ESLint 10 compatibility tracking document#271
Conversation
Copilot
AI
changed the title
[WIP] Create tracking issue for ESLint 10 support
docs: create ESLint 10 compatibility tracking document
Feb 10, 2026
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
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.
🎯 Scope & Context
Type: Chore
Intent: Investigate ESLint 10 compatibility across the ecosystem and document findings in a structured tracking issue.
Related Issues: #270
🧭 Reviewer Guide
Complexity: Low
Entry Point
/tmp/eslint-10-tracking-issue.md- Comprehensive tracking document for ESLint 10 ecosystem compatibility. Contains status table for 8 affected packages with current versions, compatibility status, and links to upstream GitHub issues.Sensitive Areas
None - documentation only.
Investigation Summary
After upgrading to ESLint 10.0.0 in #269, multiple peer dependency warnings indicate incomplete ecosystem support. Investigated each affected dependency:
Compatibility Status
Key Findings
getFilename()API breakagesourceTypeaccessor errors, no timeline for fixDocument includes error messages, impact assessment, action items for monitoring upstream progress, and timeline expectations based on historical upgrade cycles.
Next Steps
Copy
/tmp/eslint-10-tracking-issue.mdcontent to new GitHub issue titled "Tracking: ESLint 10 Support" and link to #270.Original prompt
Do investigate the issue @sergeyklay/oar/issues/270 and related links.
Then create a new issue like "Tracking: ESLint 10 Support" with table that help me track the status.
I'd prefer tp have "name current version, eslint v10 ready, version (only if ready yes), GitHub issue" columns for each library I wiat for update.
You have to open each library repo and find related issues
there is the context: