chore(deps): update dependency eslint-plugin-simple-import-sort to v10 #49
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.
This PR contains the following updates:
^7.0.0
->^10.0.0
Release Notes
lydell/eslint-plugin-simple-import-sort (eslint-plugin-simple-import-sort)
v10.0.0
Compare Source
This release might move some imported items with
type
around. This is a breaking formatting change (that only affects TypeScript and Flow), but only in the form of that you need to autofix your files.In previous versions,
type
specifiers came first:Now, all specifiers are sorted alphabetically, regardless of
type
:Motivation:
You might import a class for a type annotation using:
Later, you also start instantiating that class in the same file (
new MyClass()
), so you removetype
.Previously, this resulted in a messy diff due to the class moving:
Now, the sorting with the
type
keyword would be:Now there’s no reordering diff, just the
type
keyword being removed:This is consistent with [“Why sort on
from
?”][sort-from].Thanks to Jake Bailey (@jakebailey) for reporting and suggesting the fix!
v9.0.0
Compare Source
This version adds support for [eslint-plugin-svelte], and for
declare module
in TypeScript.More generally, imports and exports are now supported anywhere, by finding the set of parents of all imports and exports and working with those. Previously, the plugin only sorted imports and exports directly inside a
Program
node. For eslint-plugin-svelte anddeclare module
that didn’t cut it.This is only a breaking change if you imports or exports in
declare module
in TypeScript, and only in the form of that you need to autofix your files.v8.0.0
Compare Source
Node.js builtin modules prefixed with
node:
are now in a separate group by default (regex:^node:
), above the packages group. (Node.js builtins withoutnode:
are still sorted together with npm packages like before.)Before:
After:
This is only a breaking change if you use the
node:
prefix in imports, and only in the form of that you need to autofix your files.Configuration
📅 Schedule: Branch creation - "before 3am on the first day of the month" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate using a curated preset maintained by . View repository job log here