feat(zero-svelte): add Svelte integration package

[thomasmol]

Adds the zero-svelte package with context helpers, Query class, ViewStore, and Svelte-friendly bindings. Includes tests and Svelte plugin configuration.

Fixes https://bugs.rocicorp.dev/issue/3592

Just trying to get this working. Tested this package locally in a SvelteKit project and works OK so far

[vercel]

@thomasmol is attempting to deploy a commit to the Rocicorp Team on Vercel.

A member of the Team first needs to authorize it.

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​tanstack/​react-virtual@​3.13.26
	@​vitest/​runner@​4.1.7
	vitest@​4.1.7
	@​vitest/​coverage-v8@​4.1.7
	expo-sqlite@​56.0.4
	@​sveltejs/​vite-plugin-svelte@​6.2.4
	vite@​8.0.14
	@​op-engineering/​op-sqlite@​16.2.0
	wouter@​3.10.0
	turbo@​2.9.16
	svelte@​5.55.9
	pg@​8.21.0
	js-cookie@​3.0.8
	oxlint@​1.67.0
	ws@​8.21.0
	mockttp@​4.4.2
	semver@​7.8.1
	@​dotenvx/​dotenvx@​1.69.1
	baseline-browser-mapping@​2.10.32
	svelte-check@​4.4.8
	@​aws-sdk/​client-s3@​3.1056.0
	@​aws-sdk/​s3-request-presigner@​3.1056.0

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		Critical CVE: Vitest Browser: Exposed Browser Mode API Can Proxy CDP and Overwrite Config Files, Leading to RCE in npm @vitest/browser CVE: GHSA-g8mr-85jm-7xhm Vitest Browser: Exposed Browser Mode API Can Proxy CDP and Overwrite Config Files, Leading to RCE (CRITICAL) Affected versions: >= 5.0.0-beta.0 < 5.0.0-beta.4; >= 4.0.0 < 4.1.8; >= 3.0.0 < 3.2.5 Patched version: 4.1.8 From: pnpm-lock.yaml → npm/vitest@4.1.7 → npm/@vitest/browser@4.1.7 ℹ Read more on: This package | This alert | What is a critical CVE? 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: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@vitest/browser@4.1.7. 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 @expo/cli is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → npm/expo-sqlite@56.0.4 → npm/@expo/cli@56.1.13 ℹ 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/@expo/cli@56.1.13. 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 @internationalized/date is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → npm/@headlessui/react@2.2.10 → npm/@internationalized/date@3.12.2 ℹ 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/@internationalized/date@3.12.2. 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 caniuse-lite is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → npm/vite-plugin-svgr@5.2.0 → npm/vite-plugin-solid@2.11.12 → npm/@docusaurus/theme-search-algolia@3.10.1 → npm/expo-sqlite@56.0.4 → npm/@op-engineering/op-sqlite@16.2.0 → npm/postcss-preset-env@7.8.3 → npm/@docusaurus/types@3.9.2 → npm/@docusaurus/preset-classic@3.9.2 → npm/@docusaurus/core@3.9.2 → npm/caniuse-lite@1.0.30001793 ℹ 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/caniuse-lite@1.0.30001793. 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 caniuse-lite is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → npm/vite-plugin-svgr@5.2.0 → npm/vite-plugin-solid@2.11.12 → npm/@docusaurus/theme-search-algolia@3.10.1 → npm/expo-sqlite@56.0.4 → npm/@op-engineering/op-sqlite@16.2.0 → npm/postcss-preset-env@7.8.3 → npm/@docusaurus/types@3.9.2 → npm/@docusaurus/preset-classic@3.9.2 → npm/@docusaurus/core@3.9.2 → npm/caniuse-lite@1.0.30001793 ℹ 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/caniuse-lite@1.0.30001793. 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 caniuse-lite is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → npm/vite-plugin-svgr@5.2.0 → npm/vite-plugin-solid@2.11.12 → npm/@docusaurus/theme-search-algolia@3.10.1 → npm/expo-sqlite@56.0.4 → npm/@op-engineering/op-sqlite@16.2.0 → npm/postcss-preset-env@7.8.3 → npm/@docusaurus/types@3.9.2 → npm/@docusaurus/preset-classic@3.9.2 → npm/@docusaurus/core@3.9.2 → npm/caniuse-lite@1.0.30001793 ℹ 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/caniuse-lite@1.0.30001793. 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 caniuse-lite is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → npm/vite-plugin-svgr@5.2.0 → npm/vite-plugin-solid@2.11.12 → npm/@docusaurus/theme-search-algolia@3.10.1 → npm/expo-sqlite@56.0.4 → npm/@op-engineering/op-sqlite@16.2.0 → npm/postcss-preset-env@7.8.3 → npm/@docusaurus/types@3.9.2 → npm/@docusaurus/preset-classic@3.9.2 → npm/@docusaurus/core@3.9.2 → npm/caniuse-lite@1.0.30001793 ℹ 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/caniuse-lite@1.0.30001793. 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-stately is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → npm/@headlessui/react@2.2.10 → npm/react-stately@3.47.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-stately@3.47.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 webpack is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → npm/@docusaurus/theme-search-algolia@3.10.1 → npm/@docusaurus/types@3.9.2 → npm/@docusaurus/preset-classic@3.9.2 → npm/@docusaurus/core@3.9.2 → npm/webpack@5.107.2 ℹ 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/webpack@5.107.2. 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

[arv]

Thanks. This looks pretty great. I will have to review it in greater details.

FYI @stolinski

[thomasmol]

Thank you! Let me know if it needs changes. It is indeed heavily based on https://github.com/stolinski/zero-svelte

[thomasmol]

FYI for anyone looking for Svelte support with latest version of Zero, there is a workaround:

Add context.ts, query.svelte.ts and query.svelte.ts of this PR directly in your project in your lib folder (e.g. /src/lib/zero/...). You'll have to change the imports a bit to e.g. @rocicorp/zero/bindings and @rocicorp/zero. Create a client.ts like you would with https://github.com/stolinski/zero-svelte, and it should all work as expected.