chore(deps): update dependency @trivago/prettier-plugin-sort-imports to v6

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@trivago/prettier-plugin-sort-imports	4.3.0 -> 6.0.0

---

Release Notes

trivago/prettier-plugin-sort-imports (@​trivago/prettier-plugin-sort-imports)

v6.0.0

Compare Source

Breaking Changes

• Switch to ESM #​366 by @​RobbieTheWagner - The plugin now uses ES modules instead of CommonJS
• Require Node >= 20.x #​367 by @​RobbieTheWagner - Drop support for Node.js versions below 20
• Switch to vitest #​370 by @​RobbieTheWagner - Replaced Jest with Vitest for better ESM support

New features

• Ember.js gjs/gts support #​377 by @​NullVoxPopuli and @​RobbieTheWagner - Add support for Ember.js gjs/gts file formats with namespace and named type imports
• <BUILTIN_MODULES> placeholder #​381 by @​sdotson - Add support for sorting Node.js builtin modules to a specific position using <BUILTIN_MODULES> placeholder in importOrder
• <SEPARATOR> placeholder #​339 - Add <SEPARATOR> keyword for fine-grained control over import group separation when importOrderSeparation is enabled
• Sort by length option #​224 by @​KLewin23 - Add option to sort imports by import statement length
• importOrderExclude option #​384 by @​RyderKishan - Add support for excluding specific files from import sorting using glob patterns
• Expand sort-imports-ignore detection #​358 by @​ckwalsh - Improved detection of sort-imports-ignore comments throughout the file, not just at line 1

Performance improvements

• Improve removeNodesFromOriginalCode() performance #​356 by @​ckwalsh - Replace RegExp logic with string slices for better performance

Refactoring

• Stop rerendering directives #​357 by @​ckwalsh - Inject imports instead of re-rendering directives to better preserve whitespace and reduce formatting conflicts
• Stop ignoring exceptions in snapshot tests #​355 by @​ckwalsh - Improve test reliability by properly handling exceptions

Chores

• Add pnpm install command to README #​361 - Document pnpm installation option

v5.2.2

Compare Source

• Update packages and pin babel/types #​343 by @​byara

v5.2.1

Compare Source

• add svelte 5.x as peer dependency #​337 by @​werner-drklein

v5.2.0

Compare Source

• fix type import ordering #​331 by @​rsslldnphy
• Fix conditional import of prettier-plugin-svelte #​332 by @​rsslldnphy

v5.1.0

Compare Source

• Fix svelte packages being required all the time #​327 by @​byara

v5.0.1

Compare Source

• Clean up unwanted packages and unpin dependencies #​322 by @​byara

v5.0.0

Compare Source

New features

• Type imports #​153 by Xenfo
• Svelte support #​310 by canarddemagret
• Side effect import support #​320 by blutorange and vladislavarsenev
• Fixed dollar sign group replace in Vue #​283 by adamDilger
• Support importOrderImportAttributesKeyword #​273 by chentsulin

---

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.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[changeset-bot]

⚠️ No Changeset found

Latest commit: ff0cb78

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
nextjs14-dashboard	Ready	Preview	Comment	Nov 4, 2025 11:50am

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​trivago/​prettier-plugin-sort-imports@​4.3.0 ⏵ 6.0.0				-5

View full report

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed everything up to ff0cb78 in 1 minute and 14 seconds. Click for details.

• Reviewed 13 lines of code in 1 files
• Skipped 2 files when reviewing.
• Skipped posting 1 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. package.json:34

• Draft comment:
  Upgrading @trivago/prettier-plugin-sort-imports to v6.0.0 introduces breaking changes (ESM support, Node ≥20 requirement). Consider updating the Node engine in package.json (currently '>=18') to avoid compatibility issues.
• Reason this comment was not posted:
  Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 10% vs. threshold = 50% This comment is about a dependency change. The rules explicitly state "Do NOT comment on dependency changes, library versions that you don't recognize, or anything else related to dependencies." This is a clear dependency version upgrade, and the comment is asking the author to consider updating the Node engine requirement. Even though the comment might be technically correct about breaking changes, it falls under the category of dependency changes which should be ignored according to the rules. The comment does provide specific, actionable information about a potential compatibility issue. It's not just commenting on the dependency change itself, but pointing out a concrete incompatibility between the new dependency version and the existing Node engine specification. This could be seen as a legitimate code quality or compatibility concern rather than just a dependency comment. While the comment does identify a potential compatibility issue, the rules are explicit: "Do NOT comment on dependency changes, library versions that you don't recognize, or anything else related to dependencies." The comment is fundamentally about a dependency upgrade and its implications. If the dependency truly requires Node 20+, this would likely be caught during installation or runtime, not requiring a PR comment. This comment should be deleted because it violates the rule against commenting on dependency changes. The comment is about the implications of upgrading a dependency version, which falls squarely under "anything else related to dependencies."

Workflow ID: wflow_SMBt4taUfvnGrlC5

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}