feat: Svelte-renderer

[dummdidumm]

This PR introduces a new @json-render/svelte package that adds Svelte 5 support.

I've added two standalone examples (one very simple, one chat app; basically clone of the react version) and also added a Svelte version to the vite-renderers example.

The API closely aligns with that other the others.

[vercel]

@dummdidumm is attempting to deploy a commit to the Vercel Labs 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
	@​sveltejs/​adapter-auto@​7.0.1
	@​ai-sdk/​svelte@​4.0.100
	@​sveltejs/​package@​2.5.7
	@​sveltejs/​kit@​2.53.2
	@​sveltejs/​vite-plugin-svelte@​6.2.4
	satori@​0.19.2 ⏵ 0.19.3	+2		+1	-2
	tailwindcss@​4.2.1
	tailwind-variants@​3.2.2
	@​internationalized/​date@​3.11.0
	svelte@​5.53.5
	@​tailwindcss/​vite@​4.2.1
	bits-ui@​2.16.2
	lucide-svelte@​0.500.0
	@​lucide/​svelte@​0.561.0
	svelte-check@​4.4.3
	@​testing-library/​svelte@​5.3.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 svelte is 91.0% likely obfuscated Confidence: 0.91 Location: Package overview From: examples/svelte-chat/package.json → npm/svelte@5.53.5 ℹ 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/svelte@5.53.5. 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 svelte2tsx is 91.0% likely obfuscated Confidence: 0.91 Location: Package overview From: pnpm-lock.yaml → npm/@sveltejs/package@2.5.7 → npm/svelte2tsx@0.7.51 ℹ 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/svelte2tsx@0.7.51. 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

[vercel]

Additional Suggestions:

1. User message is duplicated in the API request payload in Svelte's createChatUI and Vue's useChatUI due to synchronous state update before building historyForApi.

2. $computed prop expressions in the Svelte renderer silently fail because the functions map is never threaded through to ElementRenderer's PropResolutionContext.

[ctate]

@dummdidumm Really nice work on this! Thank you!