Update dependency eslint-plugin-simple-import-sort to v10 #46
No reviewers
Labels
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: procyon/seedling#46
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "renovate/eslint-plugin-simple-import-sort-10.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.This PR has been generated by Renovate Bot.