-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
chore(deps): update dependency eslint-plugin-simple-import-sort to v10 #6391
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
chore(deps): update dependency eslint-plugin-simple-import-sort to v10 #6391
Conversation
Thanks for the PR, @renovate[bot]! typescript-eslint is a 100% community driven project, and we are incredibly grateful that you are contributing to that community. The core maintainers work on this in their personal time, so please understand that it may not be possible for them to review your work immediately. Thanks again! 🙏 Please, if you or your company is finding typescript-eslint valuable, help us sustain the project by sponsoring it transparently on https://opencollective.com/typescript-eslint. |
✅ Deploy Preview for typescript-eslint ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
This PR contains the following updates:
^9.0.0
->^10.0.0
Release Notes
lydell/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!
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), 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. View repository job log here.