Fix dark-mode usage panel and refresh dependencies

[markwylde]

Summary

• load Prism defaults before the demo theme so the Usage panel respects dark mode
• upgrade the direct development toolchain and refresh transitive dependencies
• migrate Biome and TypeScript build configuration for the new major versions
• add weekly Dependabot checks with a two-day cooldown for version updates
• clear the current npm security audit findings

Verification

• npm run typecheck
• npm run ci:biome
• npm test (18 tests)
• npm run build
• npm run build:demo
• npm audit --audit-level=low (0 vulnerabilities)

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​types/​react-dom@​19.2.3 ⏵ 19.2.4	+1		+1	+2
	@​types/​react@​19.2.7 ⏵ 19.2.18	+1		+1
	vitest@​4.0.15 ⏵ 4.1.10		+75		-1
	vite@​7.2.7 ⏵ 8.2.1	+1	+31		-1
	react@​19.2.3 ⏵ 19.2.8
	jsdom@​27.3.0 ⏵ 29.1.1	-10		+1	+6
	@​testing-library/​react@​16.3.0 ⏵ 16.3.2
	typescript@​5.9.3 ⏵ 7.0.2			-1		+10
	@​testing-library/​user-event@​14.6.1 ⏵ 14.6.3				+6
	react-dom@​19.2.3 ⏵ 19.2.8
	@​testing-library/​jest-dom@​6.9.1 ⏵ 7.0.0	+1
	@​vitejs/​plugin-react@​5.1.2 ⏵ 6.0.5	+1			+4
	@​biomejs/​biome@​2.3.8 ⏵ 2.5.7	+1			+1

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 data-urls is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: package-lock.json → npm/jsdom@29.1.1 → npm/data-urls@7.0.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/data-urls@7.0.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.

View full report