-
-
Notifications
You must be signed in to change notification settings - Fork 42
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
Tasks to make Svelte official ESLint plugin #431
Comments
great to see that this plugin is now part of @sveltejs! looks like the link in the about section on github needs to be updated to https://sveltejs.github.io/eslint-plugin-svelte/ |
Yeah, I'm no longer able to edit it as the repositories have been transferred.
Thanks! |
I requested @Rich-Harris about the authority yesterday on Discord, so I hope we can update this today. |
I discussed with maintainers and we decided that we don't change package names.👍 @ota-meshi |
Thanks to @baseballyama, we completed all the necessary tasks. Thank you! |
I would like to list tasks to make this package the default eslint-plugin.
Note: however, that this list has not yet taken consensus.
Renaming package names.- [ ]-> No change.eslint-plugin-svelte
->@sveltejs/eslint-plugin
?- [ ]-> No change.svelte-eslint-parser
->@sveltejs/eslint-parser
?- [ ] Add migration documentation for package name changeWhy?
section of the README.svelte
/sveltekit
installs by default from eslint-plugin-svelte3 to eslint-plugin-svelte.eslint-plugin-svelte3
toeslint-plugin-svelte
kit#9749I have a question.Should we change the package name? (I'm not against renaming)I think the new package name gives a good indication that it's official.However, the names of rules and the configs provided by this plugin, may be a bit lengthy and redundant.e.g.svelte/rule-name
->@sveltejs/rule-name
Also, current eslint-plugin-svelte users will need to migrate.Related issues:
The text was updated successfully, but these errors were encountered: