Feat/react router v8

[jona159]

Type of Change

• Dependency upgrade
• Bug fix (non-breaking change)
• Breaking change
  • e.g. a fixed bug or new feature that may break something else
• New feature
• Code quality improvements
  • e.g. refactoring, documentation, tests, tooling, ...

Implementation

Checklist

• I gave this pull request a meaningful title
• My pull request is targeting the dev branch
• I have added documentation to my code
• I have deleted code that I have commented out

Additional Information

• This PR closes #

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​radix-ui/​react-label@​2.1.8 ⏵ 2.1.11	+1
	@​radix-ui/​react-separator@​1.1.7 ⏵ 1.1.11	+1
	@​radix-ui/​react-aspect-ratio@​1.1.7 ⏵ 1.1.11	+1
	@​radix-ui/​react-toggle@​1.1.10 ⏵ 1.1.14	+1
	@​react-router/​serve@​7.15.0 ⏵ 8.2.0	+1
	@​radix-ui/​react-avatar@​1.1.10 ⏵ 1.2.2	+1		+1
	@​react-router/​node@​7.15.0 ⏵ 8.2.0	+1		-1
	@​react-router/​fs-routes@​7.14.2 ⏵ 8.2.0	+1
	@​radix-ui/​react-toggle-group@​1.1.11 ⏵ 1.1.15	+1
	@​radix-ui/​react-tabs@​1.1.13 ⏵ 1.1.17	+1		+1
	@​radix-ui/​react-switch@​1.2.6 ⏵ 1.3.3	+1		+2
	@​radix-ui/​react-hover-card@​1.1.15 ⏵ 1.1.19	+1
	@​radix-ui/​react-checkbox@​1.3.3 ⏵ 1.3.7	+1
	@​radix-ui/​react-alert-dialog@​1.1.15 ⏵ 1.1.19	+1
	@​radix-ui/​react-dialog@​1.1.15 ⏵ 1.1.19	+1			+1
	@​radix-ui/​react-dropdown-menu@​2.1.16 ⏵ 2.1.20	+1		+1
	@​radix-ui/​react-popover@​1.1.15 ⏵ 1.1.19	+1		+1
	@​radix-ui/​react-accordion@​1.2.12 ⏵ 1.2.16	+1
	@​formatjs/​intl@​4.1.10 ⏵ 4.1.16	+1			+1
	@​base-ui/​react@​1.5.0 ⏵ 1.6.0	-2
	@​radix-ui/​react-radio-group@​1.3.8 ⏵ 1.4.3	+1		+1
	@​radix-ui/​react-tooltip@​1.2.8 ⏵ 1.2.12	+1		+1	+1
	@​radix-ui/​react-toast@​1.2.15 ⏵ 1.2.19	+1		+1
	@​radix-ui/​react-scroll-area@​1.2.10 ⏵ 1.2.14	+1		+1
	@​radix-ui/​react-navigation-menu@​1.2.14 ⏵ 1.2.18	+1		+1
	react-router@​7.15.0 ⏵ 8.2.0	-21	+1		-1
	@​radix-ui/​react-select@​2.2.6 ⏵ 2.3.3			+1
	@​vitest/​ui@​4.1.8 ⏵ 4.1.10				+2
	react-i18next@​17.0.6 ⏵ 17.0.9	+1		-24	+2
	@​react-router/​dev@​7.15.0 ⏵ 8.2.0	+1
	@​react-email/​ui@​6.0.0 ⏵ 6.8.1				+1
	@​types/​nodemailer@​8.0.0 ⏵ 8.0.1	+1		+1	-2
See 43 more rows in the dashboard

View full report

[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		Obfuscated code: npm @emnapi/runtime is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: package-lock.json → npm/vite@8.1.4 → npm/@emnapi/runtime@1.11.1 ℹ 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 support@socket.dev. 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/@emnapi/runtime@1.11.1. 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.
Warn		Obfuscated code: npm @mswjs/interceptors is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: package-lock.json → npm/msw@2.15.0 → npm/@mswjs/interceptors@0.41.9 ℹ 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 support@socket.dev. 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/@mswjs/interceptors@0.41.9. 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.
Warn		Obfuscated code: npm js-yaml is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: package-lock.json → npm/swagger-ui-react@5.32.8 → npm/js-yaml@4.2.0 ℹ 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 support@socket.dev. 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/js-yaml@4.2.0. 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.
Warn		Obfuscated code: npm jsdom is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: package-lock.json → npm/jsdom@29.1.1 ℹ 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 support@socket.dev. 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/jsdom@29.1.1. 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.
Warn		Obfuscated code: npm jsdom is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: package-lock.json → npm/jsdom@29.1.1 ℹ 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 support@socket.dev. 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/jsdom@29.1.1. 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.
Warn		Obfuscated code: npm next is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: package-lock.json → npm/@react-email/ui@6.8.1 → npm/next@16.2.6 ℹ 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 support@socket.dev. 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/next@16.2.6. 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.
Warn		Obfuscated code: npm react-kapsule is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: package-lock.json → npm/react-globe.gl@2.38.0 → npm/react-kapsule@2.6.0 ℹ 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 support@socket.dev. 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/react-kapsule@2.6.0. 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.
Warn		Obfuscated code: npm yargs is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: package-lock.json → npm/msw@2.15.0 → npm/yargs@17.7.3 ℹ 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 support@socket.dev. 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/yargs@17.7.3. 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

[github-actions]

Coverage Report

Status	Category	Percentage	Covered / Total
🔵	Lines	67.36%	2198 / 3263
🔵	Statements	65.81%	2266 / 3443
🔵	Functions	64.98%	425 / 654
🔵	Branches	51.52%	1046 / 2030

File Coverage

File	Stmts	Branches	Functions	Lines	Uncovered Lines
Changed Files
app/utils.ts	10%	7.59%	7.4%	8.1%	41-49, 66-265

Generated in workflow #2767 for commit a94072b by the Vitest Coverage Report Action