📈 Tracking: Flat Config support
Problem
👋 Hi all! With flat config stabilized and ESLint v9 ~on the horizon~ _released!_, many community plugins are adding native support for flat config. The Configuration Migration Guide provides docs on how to do that. This is a tracking issue of the <strike>~50</strike> ~70 or so most popular community integrations and plugins for ESLint. We'll keep this list updated over time. > See also 📈 Tracking: ESLint v9 support for plugins additionally supporting ESLint v9. 📌 Status and Types emoji key: <ul> <li>✅ Full support released!</li> <li>🌗 Partial support released</li> <li>📦 Merged; pending release</li> <li>🏗️ PR was at least started</li> <li>📝 Issue filed; waiting for PR</li> <li>❌ Not supported; no issue filed</li> <li>❓ Unknown</li> <li>🛑 Known blocker</li> </ul> <table> <thead> <th>Name</th> <th>Status</th> <th>Types</th> <th>Issue</th> <th>Commit / PR</th> <th>Version</th> <th>Blocker</th> </thead> <tbody> <tr> <th colspan="7">Editor Extensions</th> </tr> <tr> <td> <a href="https://github.com/SublimeLinter/SublimeLinter-eslint"> Sublime Text </a> </td> <td>✅</td> <td><em>n/a</em></td> </tr> <tr> <td> <a href="https://github.com/Microsoft/vscode-eslint"> VS Code
Unverified for your environment
Select your OS to check compatibility.
1 Fix
Solution: 📈 Tracking: Flat Config support
@lydell > What counts as “supported”? Another level of "support" is for the ESLint plugin packages to have TypeScript types. I intend to have type-safe ESLint flat config in my projects, and many ESLint plugins currently don't publish types for their exports, because before flat config it was ESLint that was importing the modules, instead of consumers in their projects. Some plugin packages tha
Trust Score
4 verifications
- 1
Another level of "support" is for the ESLint plugin packages to have TypeScript
Another level of "support" is for the ESLint plugin packages to have TypeScript types. I intend to have type-safe ESLint flat config in my projects, and many ESLint plugins currently don't publish types for their exports, because before flat config it was ESLint that was importing the modules, instead of consumers in their projects. Some plugin packages that export types are broken for TypeScript in `nodenext` mode, which should be the gold standard for determining the status of TypeScript support since it's the only mode that actually reflects how CJS and ESM interop in current Node.js versio
- 2
It would be great if the tracking table in this issue description were to have a
It would be great if the tracking table in this issue description were to have another status column for TypeScript support.
Validation
Resolved in eslint/eslint GitHub issue #18093. Community reactions: 5 upvotes.
Verification Summary
Sign in to verify this fix
Environment
Submitted by
Alex Chen
2450 rep