Skip to content
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

Roadmap #966

Open
8 of 23 tasks
baseballyama opened this issue Dec 14, 2024 · 3 comments
Open
8 of 23 tasks

Roadmap #966

baseballyama opened this issue Dec 14, 2024 · 3 comments

Comments

@baseballyama
Copy link
Member

baseballyama commented Dec 14, 2024

Version 2 (Current Major Version)

  • Svelte Support:
    • Support for Svelte 3 and 4
    • Experimental support for Svelte 5
  • ESLint Support:
    • Targeting ESLint v7 and above
  • Node.js Support:
    • Requires Node.js v14.17 and above

Version 3 (Work in Progress)

And issues which has v3 label.
https://github.com/sveltejs/eslint-plugin-svelte/issues?q=is%3Aopen+is%3Aissue+label%3Av3

Version 4 (In Planning)

  • Svelte Support:
    • Continued support for Svelte 3 and 4
    • Enhanced rules and integrations for Svelte 5
  • ESLint Support:
    • Targeting ESLint v9 and above
  • Node.js Support:
    • Requires Node.js v18.20.4 or above
  • Rule Improvements:
    • Strengthen and refine rules for Svelte 5-specific features
    • Potential migration guides and rule deprecation notices for older Svelte versions
@baseballyama baseballyama pinned this issue Dec 14, 2024
@baseballyama baseballyama mentioned this issue Dec 14, 2024
@afonsograca
Copy link

👋
thank you for this. I wanted to ask if there's any improvements regarding ESLint 9 with TypeScript planned for version 3, or if we should still rely on typescript-eslint-parser-for-extra-files

@baseballyama
Copy link
Member Author

@afonsograca

My understanding is that there hasn’t been any action taken on the typeScript-eslint side, so we still need to use typescript-eslint-parser-for-extra-files.
Reference: typescript-eslint/typescript-eslint#6532

If you have any additional information, @ota-meshi, I would appreciate your input.

@afonsograca
Copy link

my interpretation is that the typeScript-eslint team believes that this is an external issue to them, that is why typescript-eslint/typescript-eslint#6532 and typescript-eslint/typescript-eslint#2865 being closed, with the latter labelled as wontfix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants