[codex] Update npm dependencies

[petercr]

What changed

• Refreshed npm workspace dependency pins in package-lock.json.
• Migrated Biome config to the 2.5 schema and excluded generated Playwright artifacts/raw SVGs from linting.
• Added workspace source path mappings for @santan/shared in frontend and studio TypeScript configs.
• Updated loader tests to mock TanStack Start server functions under the newer runtime expectations.
• Fixed lint/build fallout around SVG accessibility, JSON-LD script rendering, global style logging, and Sanity type literal extraction.
• Adjusted the contact e2e assertion to match the app behavior when an error node is removed.

Why

The dependency refresh pulled newer toolchain behavior from Biome, TanStack Start, and related packages. These small compatibility fixes keep linting, type-checking, build, and tests passing with the updated lockfile.

Validation

• npm run lint
• npm run type-check
• npm run build
• npm run vitest
• npm test: 28 passed, 5 skipped content-dependent post tests

Notes

npm audit still reports transitive Sanity/Vite-related advisories that require breaking/major changes to resolve.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
ccw	Ready	Preview, Comment	Jun 16, 2026 4:09am

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​tailwindcss/​oxide-linux-arm64-musl@​4.2.2 ⏵ 4.3.1
	@​tailwindcss/​oxide-linux-x64-gnu@​4.2.2 ⏵ 4.3.1
	@​tailwindcss/​oxide-linux-x64-musl@​4.2.2 ⏵ 4.3.1
	@​tailwindcss/​oxide-win32-x64-msvc@​4.2.2 ⏵ 4.3.1
	@​tanstack/​nitro-v2-vite-plugin@​1.154.9 ⏵ 1.155.0				+1
	@​tanstack/​react-query-devtools@​5.99.0 ⏵ 5.101.0				-1
	@​tanstack/​react-router-devtools@​1.166.13 ⏵ 1.167.0	+1		+1
	@​commitlint/​cli@​20.5.0 ⏵ 20.5.3	+1
	@​tanstack/​react-router-ssr-query@​1.166.12 ⏵ 1.167.1
	@​tanstack/​react-router@​1.169.2 ⏵ 1.170.15	-1
	@​tanstack/​router-plugin@​1.167.35 ⏵ 1.168.18	+1			-1
	@​types/​react@​19.2.14 ⏵ 19.2.17
	vitest@​4.1.4 ⏵ 4.1.8	+1		+1	+2
	react-router@​7.14.0 ⏵ 7.17.0	+1	+24	+1
	@​tanstack/​devtools-vite@​0.6.0 ⏵ 0.6.1
	groq@​5.24.0 ⏵ 5.31.1
	@​types/​node@​25.6.0 ⏵ 25.9.3	+1		+1
	jsdom@​29.0.2 ⏵ 29.1.1			+1
	tsx@​4.21.0 ⏵ 4.22.4	+1		+1
	vite@​7.3.3 ⏵ 7.3.5	+1	+18	+1	+2
	@​tanstack/​react-start@​1.167.65 ⏵ 1.168.25	+1		+1	-1
	tailwindcss@​4.2.2 ⏵ 4.3.1
	react@​19.2.6 ⏵ 19.2.7
	turbo@​2.9.6 ⏵ 2.9.18		+3
	@​tanstack/​react-devtools@​0.10.2 ⏵ 0.10.5
	@​tanstack/​react-query@​5.99.0 ⏵ 5.101.0
	@​tailwindcss/​vite@​4.2.2 ⏵ 4.3.1	+1		+1
	react-dom@​19.2.6 ⏵ 19.2.7
	@​sanity/​client@​7.22.0 ⏵ 7.22.1	+1
	@​portabletext/​react@​6.0.3 ⏵ 6.2.0
	@​sanity/​preview-url-secret@​4.0.4 ⏵ 4.0.7				-1
	@​commitlint/​config-conventional@​20.5.0 ⏵ 20.5.3
See 8 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 date-fns is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: package-lock.json → npm/sanity-plugin-documents-pane@3.0.2 → npm/sanity@5.31.1 → npm/date-fns@4.4.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/date-fns@4.4.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 js-yaml is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: package-lock.json → npm/@commitlint/cli@20.5.3 → npm/@tanstack/react-start@1.168.25 → 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: apps/frontend/package.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: apps/frontend/package.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.

View full report