# Svelte Svelte is a UI framework that uses a compiler to create concise web components with HTML, CSS, and JavaScript, and is free open-source software under the MIT license. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## How to Use Svelte and Go to Build a Video Chat App DevFeed: [How to Use Svelte and Go to Build a Video Chat App]() Original publisher: [Read original article]() Author: Donal Toomey Published: 2026-08-28T00:00:00Z Content type: tutorial Language: en Sources: [Twilio Blog]() Topics: [Svelte](), [Go Language](), [Vite](), [REST API](), [Single-page application (SPA)](), [Back end](), [Front end]() Tags: [api](), [build-video-app](), [build-video-chat-app](), [cors](), [developer-insights](), [env-file-security](), [environment-variables](), [git](), [go](), [how-can-i-build-a-video-app](), [how-to](), [how-to-create-video-chat-app](), [how-to-make-video-chat-app](), [live-video-chat-app](), [node-js](), [npm](), [real-time](), [svelte](), [twilio-golang](), [twilio-programmable-video](), [twilio-video](), [twilio-video-tutorial](), [video-api](), [video-app](), [video-chat-app](), [vite]() ### AI overview This tutorial explains how to build a real-time video chat app using Svelte for the frontend, Go for the backend, and the Twilio Video API. It covers the application flow, project setup, dependencies, environment configuration, and credential handling. ### Source excerpt Build a real-time video chat app with Svelte 5, Vite, and Go using the Twilio Video API. ## The SvelteKit 3 Release Candidate is here DevFeed: [The SvelteKit 3 Release Candidate is here]() Original publisher: [Read original article]() Author: The Svelte team Published: 2026-08-13T00:00:00Z Content type: release Language: en Sources: [Svelte blog]() Topics: [Svelte](), [migration](), [Code](), [configuration](), [TypeScript](), [App]() Tags: [code](), [dev](), [documentation](), [feature](), [guide](), [migration](), [release](), [svelte](), [typescript]() ### AI overview SvelteKit 3 has reached the release candidate phase, introducing breaking changes from SvelteKit 2 alongside migration tooling, updated configuration in vite.config.ts, and a shift from the $lib alias to Node subpath imports. ### Source excerpt SvelteKit 3 is now in the Release Candidate phase. If all goes well -- meaning that people like you try it out and find that it works as expected -- we will follow it up with a stable release in the near future, with no further breaking changes. But there are some breaking changes since SvelteKit 2. We're taking advantage of this release to prune some of the weeds in the codebase and lay the groundwork for SvelteKit's continued evolution, more on which below. To migrate an existing app, you can use the next version of sv migrate: npx sv@next migrate sveltekit-3 --tasks all --confirm This will automatically migrate as much of your code as possible. For everything else, it will generate a TODO list for you (or your clanker of choice) to work through. Wherever possible, SvelteKit will print useful diagnostic warnings and errors if you try to run code that hasn't yet been updated. To create a new app, run sv create: npx sv@next create my-new-app What's changed? For the full list of changes, consult the migration guide over on next.svelte.dev which is where the SvelteKit 3 documentation will live until the stable release. Most changes are fairly minor, but a few are worth calling out: Configuration now lives in vite.config.ts Previously, you would configure SvelteKit via a svelte.config.js file. This turned out to be limiting: it's useful for the Vite plugin to have access to your config immediately rather than having to go through an asynchronous resolution process (which can't begin until after we've resolved the entire Vite config, because tools like Vitest may run with a current working directory that isn't the project root), and after all why wouldn't we put the config in one place rather than two? The $lib alias is now #lib In SvelteKit 2, you would put shared code in src/lib and import it via a $lib alias. This is nicer than importing from ../../../../somewhere, which is what inevitably happens in larger codebases. But in modern projects, aliases are unnecessary, be ## What's new in Svelte: August 2026 DevFeed: [What's new in Svelte: August 2026]() Original publisher: [Read original article]() Author: Dani Sandoval Published: 2026-08-01T00:00:00Z Content type: news Language: en Sources: [Svelte blog]() Topics: [Svelte](), [releases](), [Routing (disambiguation)](), [API](), [tracing](), [Availability]() Tags: [api](), [availability](), [changelog](), [forms](), [news](), [releases](), [routing](), [svelte](), [tracing](), [validation]() ### AI overview An August 2026 roundup of Svelte and SvelteKit updates, led by the first SvelteKit 3 preview releases. It covers new modules, improved service-worker support, built-in shallow routing, remote-form changes, validation improvements, production sourcemaps, tracing, deployment detection, and related stable-line updates. ### Source excerpt The biggest news this month is the first @next releases of SvelteKit 3. Thirteen preview versions shipped in July: previewing new $app/manifest and $app/service-worker modules, improved API availability and type checking in service workers, tracing out of the experimental namespace, shallow routing baked into goto and a lot more. It's a prerelease, but it's worth trying out to see what's coming to SvelteKit! Alongside the preview releases, the stable line kept moving with submitted on remote forms and a new home for defineEnvVars. The language tools also picked up zero-config +error.svelte props so error pages get their page and error types with no extra setup. And, in case you missed it, Svelte Summit Ljubljana 2026 is happening November 19-20, with a workshop day on November 18, the day before the summit. Save the date! What's new in SvelteKit Remote forms now expose a submitted property so you can react to the moment a form is submitted without waiting for the response (2.69.0, Docs, #14811) defineEnvVars has moved from @sveltejs/kit to @sveltejs/kit/env so environment helpers live in a dedicated subpath (2.70.0, Docs, #16378) SvelteKit 3 preview The next major version has landed in @next. Here are the highlights from 3.0.0-next.5 through 3.0.0-next.13 that you'll actually want to try out: Shallow routing is now built into goto via a new state option (with persistState: true to keep state across reloads), replacing pushState and replaceState (3.0.0-next.13, #16449) goto's noScroll and keepFocus options (and their matching data-sveltekit-* attributes) collapse into a single reset option (3.0.0-next.13, #16558) error(status, {...}) is deprecated in favor of error(status, message, {...}) so error messages are always required (3.0.0-next.13, #16540) refreshAll replaces invalidateAll, which is now deprecated (3.0.0-next.8, #16289) A new $app/manifest module exposes immutable, assets, prerendered and routes so you can introspect the build output at runtime (3.0.0-next. ## Latest MCP spec now supported in mcp-handler DevFeed: [Latest MCP spec now supported in mcp-handler]() Original publisher: [Read original article]() Author: Andrew Qu Published: 2026-07-30T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [MCP Server](), [Model Context Protocol](), [Node.js](), [TypeScript](), [Next.js](), [Nuxt.js](), [Redis](), [Svelte]() Tags: [2026](), [mcp](), [mcp-server](), [model-context-protocol](), [next-js](), [node-js](), [redis](), [release](), [svelte](), [typescript]() ### AI overview mcp-handler 2.0.0 supports the 2026-07-28 Model Context Protocol specification and MCP TypeScript SDK v2. It adds native stateless protocol support, compatibility with 2025-era Streamable HTTP clients, and operation without Redis or session storage. ### Source excerpt mcp-handler@2.0.0 is now available with support for the 2026-07-28 Model Context Protocol specification and MCP TypeScript SDK v2. We originally built mcp-handler to make it easier to spin up MCP servers on popular web frameworks including Next, Nuxt, Svelte, and more. With the new 2.0 release, the handler now supports: The stateless 2026-07-28 protocol, served natively, including per-request metadata and server/discover A stateless compatibility layer for clients using 2025-era Streamable HTTP Both protocols with no Redis dependency or session storage Existing stateless Streamable HTTP clients can continue connecting to the same /mcp endpoint while servers adopt the latest protocol. Install the new packages: Create a Next.js route handler: MCP clients can connect to /api/mcp. Get started with the Next.js MCP server template, updated for mcp-handler 2.0. Before you upgrade Version 2 requires Node.js 20 or later and zod4, and replaces @modelcontextprotocol/sdk with @modelcontextprotocol/server. Tool, prompt, and resource definitions now use the SDK v2 registration APIs and Standard Schema inputs, such as registerTool with z.object(...). The deprecated HTTP+SSE transport has been removed. Requests to /sse and /message return 410 Gone. If your clients still depend on that transport, remain on mcp-handler 1.x while migrating them to Streamable HTTP. Read more ## What's new in Svelte: July 2026 DevFeed: [What's new in Svelte: July 2026]() Original publisher: [Read original article]() Author: Dani Sandoval Published: 2026-07-01T00:00:00Z Content type: news Language: en Sources: [Svelte blog]() Topics: [Svelte](), [Vite](), [Command-line interface](), [data](), [Web Development]() Tags: [cli](), [css](), [features](), [forms](), [html](), [remote](), [server](), [svelte](), [tools](), [types]() ### AI overview SvelteKit's July 2026 updates preview a simpler configuration model centered on Vite, introduce explicit typed environment variables, improve remote functions, queries, forms, prerendering, and URL handling, and bring the CLI and language tools into alignment with newer Svelte syntax. ### Source excerpt This month brought a real shift in how SvelteKit projects are configured. You can now define your SvelteKit config directly inside vite.config.js and skip svelte.config.js entirely. We also got the first preview of explicit environment variables, which will eventually replace $env/* modules in SvelteKit 3. On top of that, the language tools and the sv CLI both caught up with Svelte's new {const ...} declaration tags, so the whole toolchain is now in sync. Let's dive in! What's new in SvelteKit You can now pass your SvelteKit config directly to the Vite plugin, so a separate svelte.config.js is no longer required, as a preview of how Kit 3 will require config to live in vite.config.js (2.62.0, Docs, #15944) Experimental explicit environment variables let you declare and type your env vars in one place, as a preview of how $env/* will work in SvelteKit 3 (2.63.0, Docs, #15934) Remote function commands can now receive File objects directly, so you can upload files without manually wrapping them in FormData (2.64.0, Docs, #15978) Remote queries can now refresh other queries, making it easier to invalidate related data after a mutation (2.65.0, Docs, #16012) Prerendered .md and .mdx files are now precompressed alongside HTML, JS and CSS for faster delivery (2.66.0, Docs, #15893) SvelteKit now warns when boolean fields in remote form schemas are not marked optional, which is a common cause of silent submit failures (2.66.0, Docs, #15804) The new prerender.handleInvalidUrl option lets you customize how invalid URLs found during crawling are reported (2.67.0, Docs, #16088) RemoteFormEnhanceInstance and RemoteFormEnhanceCallback are now exported types, so you can type your custom enhance callbacks directly (2.68.0, Docs, #15816) Submitted submit fields now keep their value in the form action payload, which makes multi-button forms easier to handle on the server (2.68.0, Docs, #15979) For all the features and bugfixes that landed this month, check out the SvelteKit / Adapter ## What's new in Svelte: May 2026 DevFeed: [What's new in Svelte: May 2026]() Original publisher: [Read original article]() Author: Dani Sandoval Published: 2026-05-01T00:00:00Z Content type: release Language: en Sources: [Svelte blog]() Topics: [Svelte](), [TypeScript](), [Command-line interface](), [releases](), [Caching](), [Forms](), [dev-tools]() Tags: [caching](), [cli](), [dev-tools](), [forms](), [release](), [svelte](), [typescript]() ### AI overview A May 2026 roundup of Svelte and SvelteKit updates, including TypeScript 6.0 support, remote function and form improvements, caching changes, experimental Svelte CLI community add-ons, and selected community projects. ### Source excerpt This month we got a ton of improvements to SvelteKit's remote functions, TypeScript 6.0 support and the experimental release of community plugins in the Svelte CLI. Svelte was also featured in ThoughtWorks Technology Radar! Big month, bigger showcase... so let's dive in! What's new in SvelteKit SvelteKit now supports TypeScript 6.0 (2.56.0, Docs, #15595) form fields can now specify a default value using field.as(type, value), reducing boilerplate for pre-populated forms (2.56.0, Docs, #15577) Remote function transport now uses hydratable, enabling richer data types in query results (2.56.0, #15533) Form submit now returns a boolean to indicate submission validity for enhanced form remote functions (2.57.0, Docs, #15530) Remote Function Breaking Changes (2.56.0) Client-requested query refreshes must obtain permission from the server (#15562) Stabilize remote function caching by sorting object keys (#15570) Add run() method to queries, disallow awaiting queries outside render (#15533) Isolate command-triggered query refresh failures per-query (#15562) requested now requires limit and yields { arg, query } entries rather than validated args (#15739) Looking for more details on the many bug fixes and performance optimizations from this month? Check out the SvelteKit / Adapter CHANGELOGs. What's new in Svelte and Svelte Dev Tools Community add-ons are now available in sv as an experimental feature (sv@0.1.0, Docs, #1020) The sv and sv-utils packages are now separate in the CLI package - leading to a more explicit public API and a deprecation pass for old features (sv@0.2.0, Docs, #1046) sv will now more reliably detect if Vitest v3 is installed when configuring projects (sv@0.15.2, #1073) Types for TweenOptions, SpringOptions, SpringUpdateOptions and Updater are now available as exports from svelte/motion (svelte@5.55.0, Docs, #17967) For a full list of changes - including all the important bugfixes that went into the releases this month - check out the Svelte compiler's ## What's new in Svelte: April 2026 DevFeed: [What's new in Svelte: April 2026]() Original publisher: [Read original article]() Author: Dani Sandoval Published: 2026-04-01T00:00:00Z Content type: release Language: en Sources: [Svelte blog]() Topics: [Svelte](), [changelog](), [releases](), [configuration](), [Server]() Tags: [bug](), [changelog](), [docs](), [mcp](), [performance](), [releases](), [svelte](), [types]() ### AI overview Svelte's April 2026 update highlights a new best-practices guide, easier Svelte MCP and OpenCode integration, expanded configuration APIs, additional motion types, server-side error boundaries, and improved parameter type narrowing. It also points readers to compiler and SvelteKit changelogs for bug fixes and performance work, followed by a community showcase. ### Source excerpt This month, a new best practices guide was added to the Svelte docs. Check it out, if you haven't already! On the code side, the Svelte MCP got even easier to use with improvements to the official OpenCode package. Combined with the improvements to svelte.config.js, server-side error boundaries in SvelteKit and better types all around, this month is full of great improvements! As always, there's plenty in the showcase too! What's new in Svelte and SvelteKit MCP: Svelte's OpenCode config can now be found in sv's .opencode/ folder - including the generated svelte.json plugin config (sv@0.12.6, Docs, #977) svelte.config.js now contains functions for setting certain options (css, runes, customElement) so that there's a single source of truth for everything that needs to interact with Svelte config (svelte@5.54.0, Docs, #17951) svelte/motion now exports TweenOptions, SpringOptions, SpringUpdateOptions and Updater - these types cover the public method signatures of spring and tweened (svelte@5.55.0, Docs, #17967) Error boundaries are now allowed to catch errors on the server (kit@2.54.0, Docs, #15308) Page and layout params with matchers are now type narrowed in $app/types - leading to better type safety when working with params in $app/types, $app/state, and hooks (kit@2.55.0, Docs, #15502) For a full list of changes - including all the important bugfixes that went into the releases this month - check out the Svelte compiler's CHANGELOG. Looking for more details on the many bug fixes and performance optimizations from this month? Check out the SvelteKit / Adapter CHANGELOGs. Community ShowcaseApps & Sites built with Svelte Ghostty Config is a beautiful intuitive configuration generator for Ghostty terminal Orbit PDF is a professional, high-performance PDF toolkit that runs entirely in your browser Estimate Quest is a game-inspired planning poker experience that helps Scrum Masters and Product Managers run structured, actually engaging estimation sessions Deltaray is a fr ## Full-code apps: React and Svelte on Windmill DevFeed: [Full-code apps: React and Svelte on Windmill]() Original publisher: [Read original article]() Author: Ruben Fiszel Published: 2026-03-30T00:00:00Z Content type: release Language: en Sources: [Windmill Blog]() Topics: [React](), [Svelte](), [API](), [Back end](), [Development](), [App]() Tags: [api](), [backend](), [build](), [code](), [dev](), [development](), [launch-week](), [react](), [svelte](), [workflow]() ### AI overview Windmill introduces full-code apps that combine React or Svelte frontends with backend runnables in more than 25 languages through a typed, auto-generated API. The feature includes a local development workflow and supports asynchronous calls for long-running tasks. ### Source excerpt Introducing full-code apps: build React or Svelte frontends connected to backend runnables in 25+ languages, with a typed API and local dev workflow. ## SvelteKit Payments: The Complete Integration Guide DevFeed: [SvelteKit Payments: The Complete Integration Guide]() Original publisher: [Read original article]() Author: Ayush Agarwal Published: 2026-03-23T00:00:00Z Content type: tutorial Language: en Sources: [Dodo Payments Blog]() Topics: [Svelte](), [SDKs](), [HTML]() Tags: [checkout](), [developer-tools](), [guide](), [how-to](), [integration](), [payment-processing](), [payments](), [server-side-rendering](), [subscription](), [webhooks]() ### AI overview A tutorial on integrating Dodo Payments into SvelteKit applications. It covers SDK setup, checkout components, server-side session creation, form actions, webhook handling, and subscription-status checks, with Dodo Payments serving as the Merchant of Record for tax and compliance responsibilities. ### Source excerpt How to add payment processing to SvelteKit apps using Dodo Payments. Covers checkout components, server hooks, form actions, and webhook handling for subscriptions. ## Laravel February Product Updates DevFeed: [Laravel February Product Updates]() Original publisher: [Read original article]() Author: Laravel Team Published: 2026-03-02T16:19:42Z Content type: news Language: en Sources: [Laravel Blog]() Topics: [Laravel](), [API](), [Command-line interface](), [Artificial Intelligence](), [vercel ai sdk](), [MCP Server](), [MySQL](), [Svelte](), [vs-code](), [observability](), [npm](), [OpenClaw]() Tags: [agents](), [ai](), [api](), [ci](), [ci-cd](), [cli](), [cloud-infrastructure](), [code](), [database](), [developer-experience](), [ecosystem](), [embeddings](), [framework](), [infrastructure](), [integration](), [laravel](), [mcp](), [mysql](), [product](), [updates]() ### AI overview Laravel's February product updates include AI SDK default model configuration, a Svelte starter kit, and VS Code test runner integration. Laravel Cloud adds a programmable API and CLI, with a MySQL 8.0 end-of-life notice recommending MySQL 8.4 LTS. Forge adds npm private package support, MySQL 9 provisioning, and OpenClaw servers, while Nightwatch adds an MCP server, Linear integration, and per-user filtering. ### Source excerpt Laravel Cloud API & CLI, MySQL 8.4 upgrade notice, Forge MySQL 9, Nightwatch MCP & Linear integration, and new Framework AI updates. ## What's new in Svelte: March 2026 DevFeed: [What's new in Svelte: March 2026]() Original publisher: [Read original article]() Author: Dani Sandoval Published: 2026-03-01T00:00:00Z Content type: release Language: en Sources: [Svelte blog]() Topics: [Svelte](), [reactive](), [Frameworks](), [Netlify](), [Vite]() Tags: [bug](), [frameworks](), [netlify](), [performance](), [reactive](), [releases](), [svelte]() ### AI overview Svelte's March 2026 update covers new features and fixes in Svelte, SvelteKit, and the Svelte CLI. Highlights include TrustedHTML support, server-side error boundaries, improved navigation scroll information, Vite 8 support, Netlify adapter changes, configurable redirects, and a new official better-auth addon. ### Source excerpt This month, we got a ton of new features across Svelte, SvelteKit and even the Svelte CLI. Plus, the State of JS 2025 is out and Svelte continues to hold the top spot among reactive frameworks in terms of positive sentiment. So, without further ado, let's dive in! What's new in Svelte createContext can now be used when instantiating components programmatically (svelte@5.50.0, Docs, #17575) {@html} expressions now support TrustedHTML (svelte@5.52.0, #17701) Comments are now allowed in HTML tags (svelte@5.53.0/svelte-language-server@0.17.28, #17671) Error boundaries now work on the server (svelte@5.53.0, Docs, #17672) For a full list of changes - including all the important bugfixes that went into the releases this month - check out the Svelte compiler's CHANGELOG What's new in SvelteKit hydratable's injected script now works with CSP (kit@2.51.0, #15048) Navigation callbacks (beforeNavigate, onNavigate, and afterNavigate) now include scroll position information via the scroll property on from and to targets. This enables use cases like animating transitions based on the target scroll position when using browser back/forward navigation (kit@2.51.0, Docs, #15248) Vite 8 is now supported (kit@2.53.0, #15024) The match function can map a path back to a route id and params (kit@2.52.0, Docs, #14997) Breaking (Netlify Adapter): platform.context now uses modern Netlify Functions - previously this was the AWS Lambda-style context. If you were using this in your app (unlikely), you will need to update your code to read from new fields. (adapter-netlify@6.0.0, More details, Docs, #15203) redirects can now be configured in netlify.toml - removing the limitation of only being able to configure redirects via the _redirects file (adapter-netlify@6.0.0, #15203) better-auth is now an official addon in the Svelte CLI (sv@0.12.0, #898) Looking for more details on the many bug fixes and performance optimizations from this month? Check out the SvelteKit / Adapter CHANGELOGs. Community S ## What's new in Svelte: February 2026 DevFeed: [What's new in Svelte: February 2026]() Original publisher: [Read original article]() Author: Dani Sandoval Published: 2026-02-01T00:00:00Z Content type: article Language: en Sources: [Svelte blog]() Topics: [Svelte](), [releases](), [changelog](), [Vulnerabilities](), [CSS](), [HTML](), [Parser](), [observability](), [Open Source](), [Tauri](), [Transcodings]() Tags: [changelog](), [conversion](), [css](), [developers](), [docs](), [ffmpeg](), [html](), [observability](), [open-source](), [releases](), [svelte](), [tauri](), [vulnerabilities]() ### AI overview Svelte's February 2026 update introduces improvements across Svelte and SvelteKit, including richer select-element customization, an exported CSS parser, Shadow DOM configuration, remote form changes, configurable Node server timeouts, and improved Vercel observability. The article also highlights recent ecosystem vulnerability patches, changelogs, and community projects. ### Source excerpt This month brings a few new features to Svelte and SvelteKit and quite a few new libraries from around the community. Also, in case you missed it last month, the Svelte maintainers released patches for 5 vulnerabilities across the Svelte ecosystem. So be sure you're up to date by reading the blog post, CVEs affecting the Svelte ecosystem. Now, without further ado, let's dive in... What's new in Svelte & SvelteKit To support newer browsers that allow it, you can now customize