fix(deps): update dependency @ianvs/prettier-plugin-sort-imports to ^4.7.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@ianvs/prettier-plugin-sort-imports	^4.2.0 -> ^4.7.0

---

Release Notes

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

v4.7.0

Compare Source

What's Changed

This project began as a fork because I wanted a plugin that would not move side-effect imports around and mess with my CSS cascade. So its first and most distinguishing feature is that side-effect imports do not move, and other imports are not sorted across them.

This works fine in most cases, but some people have side-effect imports that they know can be sorted safely. For those, there is now an "escape hatch" option named importOrderSafeSideEffects. It is an array of glob pattern strings (similar to importOrder) which, when they match against a side-effect import, allow that import to be sorted as if it were a standard import.

Suggestions for safe use:

• Use ^ at the start of your pattern and $ at the end, to avoid accidentally matching part of an import name. For example, "^server-only$", to avoid matching against import "not-server-only".
• Use extreme caution if matching against relative files or CSS files. If you decide to sort CSS imports and a file ever imports more than one CSS file, your cascade may change.
• You can still use // prettier-ignore to stop sorting a particular import that would otherwise be sorted.

Feedback on this feature is welcome.

Features

• Add importOrderSafeSideEffects option by @​IanVS in IanVS#240

Internal

• Clean up options & remove explicit function types by @​IanVS in IanVS#239

Full Changelog: IanVS/prettier-plugin-sort-imports@v4.6.3...v4.7.0

v4.6.3

Compare Source

What's Changed

• Revert "fix: conditionally register ember and oxc parsers when depend… by @​IanVS in IanVS#237

Full Changelog: IanVS/prettier-plugin-sort-imports@4.6.2...v4.6.3

v4.6.2

Compare Source

What's Changed

• fix: conditionally register ember and oxc parsers when dependencies available by @​jahands in IanVS#234

New Contributors

• @​jahands made their first contribution in IanVS#234

Full Changelog: IanVS/prettier-plugin-sort-imports@v4.6.1...4.6.2

v4.6.1

Compare Source

What's Changed

• Do not warn for markdown code blocks by @​IanVS in IanVS#232

Full Changelog: IanVS/prettier-plugin-sort-imports@v4.6.0...v4.6.1

v4.6.0

Compare Source

What's Changed

• Be more tolerant of babel parse errors by @​IanVS in IanVS#230
• Add support for ember template tags by @​IanVS in IanVS#231

Full Changelog: IanVS/prettier-plugin-sort-imports@v4.5.1...v4.6.0

v4.5.1

Compare Source

What's Changed

Fixes

• Short-circuit before parsing by @​IanVS in IanVS#224

Internal

• Upgrade development dependencies by @​IanVS in IanVS#223

Full Changelog: IanVS/prettier-plugin-sort-imports@v4.5.0...v4.5.1

v4.5.0

Compare Source

What's Changed

• Add @​prettier/plugin-oxc support by @​Marsup in IanVS#221
• Print full stacktrace when babel parsing errors are encountered

New Contributors

• @​Marsup made their first contribution in IanVS#221

Full Changelog: IanVS/prettier-plugin-sort-imports@v4.4.2...v4.5.0

v4.4.2

Compare Source

What's Changed

• Update peerDeps to allow prettier v4. by @​cpojer in IanVS#210
• [Internal] Update prettier dev dependency to 4.0 alpha by @​IanVS in IanVS#211

New Contributors

• @​cpojer made their first contribution in IanVS#210

Full Changelog: IanVS/prettier-plugin-sort-imports@v4.4.1...v4.4.2

v4.4.1

Compare Source

What's Changed

• fix: catch babel parse errors by @​michaelfaith in IanVS#198

New Contributors

• @​michaelfaith made their first contribution in IanVS#198

Full Changelog: IanVS/prettier-plugin-sort-imports@v4.4.0...v4.4.1

v4.4.0

Compare Source

What's Changed

Enhancements

• Re-add importOrderCaseSensitive option for case-sensitive sorting by @​acnebs in IanVS#184
• Throw an error when no matching sortOrder group by @​IanVS in IanVS#192

Maintenance

• Switch from yarn to pnpm by @​IanVS in IanVS#178
• Remove unused @​babel/core, update babel deps by @​IanVS in IanVS#191

New Contributors

• @​acnebs made their first contribution in IanVS#184

Full Changelog: IanVS/prettier-plugin-sort-imports@v4.3.1...v4.4.0

v4.3.1

Compare Source

What's Changed

• fixes readme with correct BUILTIN_MODULES setting name by @​tusharf5 in IanVS#177
• Add support for return in Astro component script by @​IanVS in IanVS#176

New Contributors

• @​tusharf5 made their first contribution in IanVS#177

Full Changelog: IanVS/prettier-plugin-sort-imports@v4.3.0...v4.3.1

v4.3.0

Compare Source

What's Changed

Features

• Add support for import attributes by @​IanVS in IanVS#174

This release adds support for experimental import attributes / assertions. There have been a number of styles proposed by TC-39 over the years, but the latest is to use import x from 'x' with { type: 'json' };, which is called an "import attribute". There is also an older "import assertion" form, which uses assert instead of with.

Note: You may need to add "importAttributes" to your "importOrderParserPlugins" option in order to support this. And if you are using the older assertion style, you'll need to add it as '[\"importAttributes\", {\"deprecatedAssertSyntax\": true}]'.

This plugin will also convert the older assertion style to import attributes.

Bugfixes

• Fix vue 2.7 support by @​IanVS in IanVS#173

TypeScript

• Augment Prettier Options types with internal PluginConfig by @​jeremy-code in IanVS#172

You can now type your prettier config as simply /** @​type {import("prettier").Config} */, and you'll also get the types for the options this plugin adds, automatically.

Docs

• Update README to show more options for disabling and overrides by @​ADTC in IanVS#165

New Contributors

• @​ADTC made their first contribution in IanVS#165
• @​jeremy-code made their first contribution in IanVS#172

Full Changelog: IanVS/prettier-plugin-sort-imports@v4.2.1...v4.3.0

v4.2.1

Compare Source

What's Changed

Bugfixes

• Detect Vue 2.7 / 3 more reliably by @​IanVS in IanVS#160
• Setting importOrder to [] should disable plugin by @​IanVS in IanVS#161

Full Changelog: IanVS/prettier-plugin-sort-imports@v4.2.0...v4.2.1

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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.

[vercel]

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

Project	Deployment	Preview	Comments	Updated (UTC)
weather-app	Ready	Preview	Comment	Aug 31, 2025 11:25am

[github-actions]

⚡️ Lighthouse report for the changes in this PR:

Category	Score
🟠 Performance	68
🟢 Accessibility	100
🟢 Best practices	100
🟠 SEO	63
🔴 PWA	undefined

Lighthouse ran on https://weather-app-git-renovate-ianv-a5cf6e-creative-programming-group.vercel.app/

[github-actions]

Running Lighthouse audit...

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	react-leaflet@​4.2.1
	react-html-parser@​2.0.2
	sonner@​1.4.3
	postcss@​8.4.35
	react-spinners@​0.13.8
	react@​18.2.0
	react-icons@​5.0.1
	start-server-and-test@​2.0.10
	sharp@​0.33.5
	prettier@​3.2.5
	react-dom@​18.2.0
	@​ianvs/​prettier-plugin-sort-imports@​4.2.0 ⏵ 4.7.0				+3
	react-hook-form@​7.51.0
	prettier-plugin-tailwindcss@​0.5.12
	resend@​3.2.0

View full report

[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.

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Join our Discord community for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore or @coderabbit ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		[email protected] has Obfuscated code. Confidence: 0.94 Location: Package overview From: pnpm-lock.yaml → npm/[email protected] ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report