# Vite Vite is a frontend build tool for web applications. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Adding Google Login to a React App with Auth0 DevFeed: [Adding Google Login to a React App with Auth0]() Original publisher: [Read original article]() Author: Carla Urrea Stabile Published: 2026-09-11T00:00:00Z Content type: tutorial Language: en Sources: [Auth0 Blog]() Topics: [Auth0](), [React](), [SDK](), [OAuth](), [OpenID connect (OIDC)](), [Vite](), [web applications](), [Node.js]() Tags: [auth0](), [authentication](), [google](), [node-js](), [oauth](), [oidc](), [react](), [sdk](), [tutorial](), [vite](), [web-applications]() ### AI overview A step-by-step tutorial for adding Google login to a Vite-based React application with Auth0. It covers installing the Auth0 React SDK, creating and configuring an Auth0 application, setting callback, logout, and web-origin URLs, and preparing credentials for production Google authentication. ### Source excerpt Add Google login to a React app with Auth0. A step-by-step tutorial from installing the Auth0 React SDK to configuring your own production Google credentials. ## 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. ## 🍔🧠 Why Linear Feels So Fast (Technical Breakdown) DevFeed: [🍔🧠 Why Linear Feels So Fast (Technical Breakdown)]() Original publisher: [Read original article]() Author: Alexandre Zajac Published: 2026-07-20T15:30:40Z Content type: article Language: en Sources: [Hungry Minds]() Topics: [Caching](), [Local-First](), [client](), [WebSocket](), [Software Engineering](), [Vite](), [npm]() Tags: [cache](), [caching](), [javascript](), [linear](), [local-first](), [npm](), [technical](), [vite](), [websocket]() ### AI overview A technical breakdown of how Linear aims to feel fast by minimizing network latency. It describes local-first state updates, asynchronous synchronization over WebSocket, code splitting, parallel module loading, service-worker precaching, and separately cached dependency chunks. ### Source excerpt PLUS: Virtual memory explained 👨💻, Spark retires vector DBs 💾, Backprop explained simply 🧮 ## Nuxt 4.5 DevFeed: [Nuxt 4.5]() Original publisher: [Read original article]() Published: 2026-07-18T00:00:00Z Content type: release Language: en Sources: [The Nuxt Blog]() Topics: [Nuxt.js](), [Vite](), [releases](), [Server-side rendering](), [Streaming](), [migration]() Tags: [dev](), [framework](), [migration](), [release](), [streaming](), [vue]() ### AI overview Nuxt 4.5 introduces major build-layer upgrades, experimental SSR streaming, stable error codes, new composables and conventions, and groundwork for Nuxt 5. It also updates Nuxt to Vite 8 and Rspack 2, while Nuxt 3 approaches end of life. ### Source excerpt Nuxt 4.5 is our biggest release in a while. Vite 8, Rspack 2 powered by Rsbuild, experimental SSR streaming, a stable error code system, a new useLayout composable, named views, and a lot of groundwork for Nuxt 5. ## 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 ## Vite 8.1 is out! DevFeed: [Vite 8.1 is out!]() Original publisher: [Read original article]() Author: The Vite Team Published: 2026-06-23T00:00:00Z Content type: release Language: en Sources: [Vite]() Topics: [Vite](), [Development](), [React]() Tags: [2026](), [announce](), [browser](), [linear](), [performance](), [release](), [vite]() ### AI overview Vite 8.1 has been released with experimental bundled dev mode, which is intended to improve development performance for large applications. Initial testing reported faster startup and full-page reloads than the unbundled dev server. ### Source excerpt Vite 8.1 is out! June 23, 2026 Vite 8 was released in March with a single unified bundler powered by Rolldown, opening the door to further improvements. It is now seeing 41.6 million weekly downloads, almost reaching the total downloads of Vite 7. Alongside resolving upgrade regressions, we've been working on new features, and we're excited to announce the release of Vite 8.1. Quick links: Docs Translations: 简体中文, 日本語, Español, Português, 한국어, Deutsch, فارسی GitHub Changelog Play online with Vite 8.1 using vite.new or scaffold a Vite app locally with your preferred framework running pnpm create vite. Check out the Getting Started Guide for more information. We invite you to help us improve Vite (joining the more than 1.2K contributors to Vite Core), our dependencies, or plugins and projects in the ecosystem. Learn more at our Contributing Guide. A good way to get started is by triaging issues, reviewing PRs, sending tests PRs based on open issues, and supporting others in Discussions or Vite Land's help forum. If you have questions, join our Discord community and talk to us in the #contributing channel. Stay updated and connect with others building on top of Vite by following us on Bluesky, X, or Mastodon. Features Experimental Bundled Dev Mode Experimental support for bundled dev mode is now available. This was previously called as "Full Bundle Mode". This mode is to improve performance of huge applications that suffer from the number of modules. In our initial testing with an app loading 10,000 React components, bundled dev mode achieved around 15x faster startup and 10x faster full page reloads compared to the unbundled dev server, while keeping HMR instant regardless of the application size. Early testing on real-world applications shows similar gains: the Linear team saw cold start rendering up to 3x faster, full reloads around 40% faster, and 10x fewer network requests. Why bundled dev mode? Vite is known for its unbundled dev server approach, which is a ## Workflow SDK now supports TanStack Start DevFeed: [Workflow SDK now supports TanStack Start]() Original publisher: [Read original article]() Author: Peter Wielander Published: 2026-06-16T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [SDKs](), [Vercel](), [Vite](), [configuration](), [TypeScript]() Tags: [config](), [guide](), [knowledge-base](), [persistence](), [queue](), [sdk](), [typescript](), [vercel](), [vite](), [workflow]() ### AI overview Vercel's Workflow SDK now supports TanStack Start applications. Because TanStack Start uses Vite and Nitro, the existing workflow/vite plugin can be added to the Vite configuration. Developers can then define durable, resumable workflow and step functions in TypeScript that survive restarts, sleep for days, and retry on failure, while the plugin handles compilation, queue configuration, and persistence. ### Source excerpt Workflow SDK now supports TanStack Start applications on Vercel. TanStack Start is built on Vite and Nitro, so the existing workflow/vite plugin works directly. Add it to vite.config.ts alongside tanstackStart(). From there, write workflow and step functions in standard TypeScript with "use workflow" and "use step". They run as durable, resumable operations that survive restarts, sleep for days, and retry on failure, with compilation, queue configuration, and persistence handled by the plugin. Read the TanStack Start guide to learn more and create your first durable workflow, or browse TanStack resources in the Vercel Knowledge Base. Read more ## Cloudflare supports Vite's mission DevFeed: [Cloudflare supports Vite's mission]() Original publisher: [Read original article]() Author: The Vite Team Published: 2026-06-04T00:00:00Z Content type: article Language: en Sources: [Vite]() Topics: [Vite](), [Cloudflare](), [Open Source](), [Web platform]() Tags: [announcement](), [blog](), [cloudflare](), [github](), [open-source]() ### AI overview Cloudflare is investing in Vite after VoidZero joins the company, while Vite remains open source, vendor-agnostic, and governed by the Vite team. Cloudflare also announced a $1 million fund for the Vite ecosystem to support maintainers, tooling, ecosystem projects, web platform work, and security improvements. ### Source excerpt Cloudflare supports Vite's mission June 4, 2026 Today marks the start of a new stage for Vite. VoidZero is joining Cloudflare. You can read the full story from Evan You in VoidZero's announcement. In Cloudflare's blog post, they explain why they are investing in the Vite stack, which has now become part of the web's foundational infrastructure. Vite's team governance, mission, and philosophy aren't changing: Vite remains open source under the MIT license. Vite remains vendor-agnostic, applications built with vite are meant to run anywhere. Vite continues to be stewarded by the Vite team, which includes members employed by different organizations and independent members. Vite's Open Collective funds are managed by the Vite team and are used to fund independent core team members, dependencies, and other key projects in the ecosystem. The Vite team members employed by VoidZero are all joining Cloudflare and will continue to work on Vite. As stated in the VoidZero and Cloudflare announcements, the same applies to Vitest, Rolldown, Oxc, and Vite+. Cloudflare's Vite Ecosystem Open Source Fund Cloudflare is committed to helping Vite remain neutral and has also announced a new $1M open source fund for the Vite ecosystem. Alongside Vite's Open Collective (which stays managed by the Vite team), these funds will allow us to further improve Vite and its ecosystem, including: Fund more popular plugins and toolings in the ecosystem. Adopt a core team member stipend to support independent team members. Work closely with teams of the Vite stack, including Rolldown, Oxc, and Vite+. Work closely with the ecosystem maintainers from frameworks, plugins, and deployment platforms. Work with standard bodies and adopt new web platform features faster. Audit and release security issues more quickly. Many of which we had already started working on, which will help accelerate the process. Thank You We want to thank our current sponsors through GitHub Sponsors and Open Collective, which ## What's new in Astro - May 2026 DevFeed: [What's new in Astro - May 2026]() Original publisher: [Read original article]() Author: Sarah Rainsberger Published: 2026-05-31T00:00:00Z Content type: article Language: en Sources: [The Astro Blog]() Topics: [Astro](), [jobs](), [Content Management System](), [releases](), [Hono](), [Routing (disambiguation)](), [Rust](), [Vite](), [Cloudflare](), [Markdown](), [Express](), [stripe]() Tags: [astro](), [cloudflare](), [developer](), [features](), [integration](), [jobs](), [learn](), [markdown](), [real-time](), [releases](), [routing](), [rust](), [stripe](), [web]() ### AI overview Astro's May 2026 ecosystem update covers the new Astro Jobs board, TinaCMS adopting Astro by default, an ImageKit integration, the Astro 7 alpha, recent Astro and Starlight releases, community adoption, showcase sites, team news, and selected community content. ### Source excerpt May 2026 - A new Astro jobs board, TinaCMS makes Astro their default template, experimental advanced routing, and more! ## How we cut build times by two-thirds by deleting our CMS DevFeed: [How we cut build times by two-thirds by deleting our CMS]() Original publisher: [Read original article]() Author: Eli Lennox Published: 2026-05-28T09:00:00Z Content type: article Language: en Sources: [Sentry Blog]() Topics: [Astro](), [Markdown](), [Claude Code](), [gatsby](), [Vite](), [React]() Tags: [astro](), [claude-code](), [code](), [development](), [markdown](), [vite]() ### AI overview Sentry describes replacing legacy Gatsby sites and a traditional headless CMS with Astro, Markdown, and Claude Code skills. The migration reduced build times from about 14 minutes to under 4 minutes and eliminated the cited CMS and marketing automation API failures. ### Source excerpt Sentry replaced its CMS with Astro, Markdown, and Claude Code skills -- cutting build times from 14 to under 4 minutes and eliminating API failures. ## My Frontend Stack In 2026 DevFeed: [My Frontend Stack In 2026]() Original publisher: [Read original article]() Author: The T-Shaped Dev Published: 2026-05-23T02:19:53Z Content type: opinion Language: en Sources: [The T-Shaped Dev]() Topics: [Front end](), [Next.js](), [Vite](), [React](), [Tailwind CSS](), [Shadcn UI](), [TypeScript](), [Single-page application (SPA)](), [Server-side rendering]() Tags: [2026](), [frontend](), [next-js](), [react](), [ssr](), [tailwind](), [tailwind-css](), [typescript](), [vite]() ### AI overview An opinionated overview of a 2026 frontend stack for production applications. The author describes choosing Next.js for content-heavy sites, Vite with React and TypeScript for internal tools and single-page applications, pnpm for package management, and Tailwind CSS with shadcn/ui for styling and components. ### Source excerpt The tools I actually reach for when building production apps, from framework to the moment a user hits a bug. ## Generate editorial React presentations with one Claude Code prompt DevFeed: [Generate editorial React presentations with one Claude Code prompt]() Original publisher: [Read original article]() Author: Ishan Khanna Published: 2026-05-17T08:17:35Z Content type: tutorial Language: en Sources: [Ishan Khanna]() Topics: [Claude Code](), [React](), [Code](), [Large Language Model](), [Tailwind CSS](), [Vite]() Tags: [animation](), [architecture](), [claude-code](), [code](), [how-to](), [keyboard](), [llm](), [llms](), [presentation](), [prompt](), [prompting](), [react](), [tailwind](), [vite]() ### AI overview A tutorial presents a detailed Claude Code prompt for generating five-slide React presentations as a single Presentation.jsx file. The prompt fixes the design system and narrative structure while allowing the topic content to change, and the result can be used in a Vite, React, and Tailwind project. ### Source excerpt If you caught my YouTube Short on generating presentations as React apps with an LLM, this is the prompt I promised. Paste it into Claude Code, edit the CONTENT block at the top, and you get back a single-file Presentation.jsx -- five slides, keyboard nav, animated counters, an ## Cloudflare's vinext Reimplements Next.js on Vite in Under a Week DevFeed: [Cloudflare's vinext Reimplements Next.js on Vite in Under a Week]() Original publisher: [Read original article]() Author: TheAnkurTyagi Published: 2026-04-08T15:49:33Z Content type: opinion Language: en Sources: [ByteSizedBets]() Topics: [Cloudflare](), [Next.js](), [Vite](), [AI-assisted coding](), [Open Source]() Tags: [ai](), [cloudflare](), [coding-agents](), [next-js](), [open-source](), [vite]() ### AI overview The article examines Cloudflare's vinext, a framework reimplementation of Next.js on Vite that Cloudflare says was built by one engineer using an AI model in under a week. It reports claimed results of 4x faster builds, 57% smaller bundles, and 94% Next.js API coverage, while discussing testing, deployment outside Vercel, and the resulting ecosystem dispute. ### Source excerpt And it only cost $1,100 ## Laravel March Product Updates DevFeed: [Laravel March Product Updates]() Original publisher: [Read original article]() Author: Laravel Team Published: 2026-04-01T22:26:49Z Content type: news Language: en Sources: [Laravel Blog]() Topics: [Laravel](), [Artificial Intelligence](), [Cloud](), [PHP](), [SDKs](), [Embeddings](), [AI search](), [text-generation](), [JSON:API](), [PostgreSQL](), [Server-side rendering](), [Vite]() Tags: [ai](), [api](), [apps](), [cloud](), [deployment](), [development](), [embeddings](), [github](), [laravel](), [observability](), [php](), [postgresql](), [product](), [search](), [text-generation](), [updates]() ### AI overview Laravel's March product updates introduce Laravel 13 with first-party AI tooling, including a unified SDK for text generation, agents, embeddings, audio, semantic search, and JSON:API resources. Laravel Cloud adds trial credits, GitHub SSO, scheduled autoscaling, and a redesigned usage page, while Forge adds managed PostgreSQL databases with observability, read replicas, and automated backups. ### Source excerpt # Laravel March Product Updates March was a big month for product updates. Laravel 13 brings first-party AI tooling to the framework, Laravel Cloud now has a free trial with no credit card required,... ## Inertia v3: What's Changed Since the First Beta DevFeed: [Inertia v3: What's Changed Since the First Beta]() Original publisher: [Read original article]() Author: Pascal Baljet Published: 2026-03-25T17:07:23Z Content type: article Language: en Sources: [Laravel Blog]() Topics: [Laravel](), [Vite](), [migration](), [Laravel Boost](), [JavaScript]() Tags: [javascript](), [laravel](), [laravel-boost](), [migration](), [release](), [updates]() ### AI overview The article summarizes changes to Inertia v3 since its first beta, including simplified layout props, updated layout APIs, a callback for configuring the root app, Vite 8 support, migration from lodash to es-toolkit, new Laravel Blade components, and a Laravel Boost upgrade prompt. ### Source excerpt What changed in Inertia v3 since the first beta: simpler layout props, Vite 8 support, a withApp callback, and new Blade components. ## Vite 8.0 is out! DevFeed: [Vite 8.0 is out!]() Original publisher: [Read original article]() Author: The Vite Team Published: 2026-03-12T00:00:00Z Content type: release Language: en Sources: [Vite]() Topics: [Vite](), [Rust](), [Optimization](), [Developer experience](), [Orchestration](), [Parser](), [npm](), [GitHub]() Tags: [changelog](), [community](), [developer](), [developer-experience](), [docs](), [guide](), [links](), [maintainers](), [optimization](), [orchestration](), [rust](), [speed]() ### AI overview Vite 8 is a stable release that replaces Vite's separate esbuild and Rollup bundlers with Rolldown, a unified Rust-based bundler. The article highlights faster builds, plugin compatibility, a new searchable plugin registry, migration resources, and ways to contribute to the Vite ecosystem. ### Source excerpt Vite 8.0 is out! March 12, 2026 We're thrilled to announce the stable release of Vite 8! When Vite first launched, we made a pragmatic bet on two bundlers: esbuild for speed during development, and Rollup for optimized production builds. That bet served us well for years. We're very grateful to the Rollup and esbuild maintainers. Vite wouldn't have succeeded without them. Today, it resolves into one: Vite 8 ships with Rolldown as its single, unified, Rust-based bundler, delivering up to 10-30x faster builds while maintaining full plugin compatibility. This is the most significant architectural change since Vite 2. Vite is now being downloaded 65 million times a week, and the ecosystem continues to grow with every release. To help developers navigate the ever-expanding plugin landscape, we also launched registry.vite.dev, a searchable directory of plugins for Vite, Rolldown, and Rollup that collects plugin data from npm daily. Quick links: Docs Translations: 简体中文, 日本語, Español, Português, 한국어, Deutsch, فارسی Migration Guide GitHub Changelog Play online with Vite 8 using vite.new or scaffold a Vite app locally with your preferred framework running pnpm create vite. Check out the Getting Started Guide for more information. We invite you to help us improve Vite (joining the more than 1.2K contributors to Vite Core), our dependencies, or plugins and projects in the ecosystem. Learn more at our Contributing Guide. A good way to get started is by triaging issues, reviewing PRs, sending tests PRs based on open issues, and supporting others in Discussions or Vite Land's help forum. If you have questions, join our Discord community and talk to us in the #contributing channel. Stay updated and connect with others building on top of Vite by following us on Bluesky, X, or Mastodon. The Rolldown-Powered Vite The problem Since its earliest versions, Vite relied on two separate bundlers to serve different needs. esbuild handled fast compilation during development (dependency ## Astro 6.0 DevFeed: [Astro 6.0]() Original publisher: [Read original article]() Author: Matthew Phillips; Emanuele Stoppa; Florian Lefebvre; Matt Kane Published: 2026-03-10T00:00:00Z Content type: release Language: en Sources: [The Astro Blog]() Topics: [Astro](), [Vite](), [Cloudflare Workers](), [Rust](), [API](), [Tooling](), [Bun](), [Deno](), [Node.js]() Tags: [astro](), [cli](), [cloudflare](), [cloudflare-workers](), [performance](), [platform](), [release](), [rust](), [scalability](), [tooling]() ### AI overview Astro 6 introduces a Fonts API, Content Security Policy API, live content collections for externally hosted content, and a refactored development server and build pipeline powered by Vite's Environment API. It also adds an experimental Rust compiler and improved support for running production runtimes such as Cloudflare Workers during development. ### Source excerpt Astro 6 is here with a refactored dev server, an experimental Rust compiler, live content collections, CSP, and more. ## Inertia.js v3 Is Now in Beta DevFeed: [Inertia.js v3 Is Now in Beta]() Original publisher: [Read original article]() Author: Pascal Baljet Published: 2026-03-05T16:54:27Z Content type: release Language: en Sources: [Laravel Blog]() Topics: [Vite](), [Server-side rendering](), [Boilerplate](), [migration](), [Node.js](), [API]() Tags: [development](), [http](), [migration](), [node-js](), [release](), [updates]() ### AI overview Inertia.js v3 has entered beta with a Vite plugin that automates page resolution and SSR, a built-in XHR client replacing Axios, and support for optimistic updates, standalone HTTP requests, and layout props. ### Source excerpt Inertia.js v3 beta is out. No more Axios, a new Vite plugin handles SSR automatically, and optimistic updates are now built in. Upgrade guide included. ## 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 ## Teaching AI to Do Auth (So You Don't Have To) DevFeed: [Teaching AI to Do Auth (So You Don't Have To)]() Original publisher: [Read original article]() Author: Pedro Figueiredo Published: 2025-12-17T17:26:10Z Content type: article Language: en Sources: [Blog -- Neon Docs]() Topics: [MCP](), [cursor](), [Claude](), [React](), [TypeScript](), [Vite]() Tags: [ai-tools](), [claude](), [cursor](), [mcp](), [product](), [react](), [typescript](), [vite]() ### AI overview The article demonstrates how Neon Auth can be integrated into existing applications with AI-assisted development. It describes using MCP with Cursor, Claude, or an IDE to scaffold authentication in a Vite, React, and TypeScript app, guided by explicit rules, prompt templates, AI skills, and current SDK documentation. ### Source excerpt We just launched Neon Auth and of course the immediate follow-up task I had was "let's teach my AI tools to use it for me". So we've been wiring Neon Auth into our MCP so you can open Cursor, Claude, or your IDE or choice and let the AI build a backend for you. Here's [...] ## Watch and Rebuild Storybook Dependencies with Nx DevFeed: [Watch and Rebuild Storybook Dependencies with Nx]() Original publisher: [Read original article]() Author: Juri Strumpflohner Published: 2025-10-29T00:00:00Z Content type: tutorial Language: en Sources: [Juri Strumpflohner]() Topics: [Storybook](), [Developer experience](), [monorepo](), [Vite](), [Library](), [configuration]() Tags: [build](), [commands](), [configuration](), [developer-experience](), [how-to](), [monorepo](), [nx](), [storybook](), [vite]() ### AI overview This tutorial explains how to use Nx workspace watching to automatically rebuild buildable library dependencies in a Storybook monorepo. It configures watch and dependency targets so Storybook's Vite HMR server detects changes and refreshes automatically. ### Source excerpt Learn how to set up automatic rebuilding of buildable library dependencies in your Storybook setup using Nx workspace watching for a seamless developer experience. ## Nuxt 4.2 DevFeed: [Nuxt 4.2]() Original publisher: [Read original article]() Published: 2025-10-25T00:00:00Z Content type: release Language: en Sources: [The Nuxt Blog]() Topics: [Nuxt.js](), [TypeScript](), [debugging](), [Vite](), [Server-side rendering]() Tags: [api](), [debugging](), [experimental](), [net](), [nuxt](), [performance](), [release](), [typescript](), [vite]() ### AI overview Nuxt 4.2 introduces experimental TypeScript developer-experience improvements, finer-grained cancellation for data-fetching requests, a detailed error overlay during development, and optional Vite Environment API support. It also extracts Nitro server integration into a separate package and lays groundwork for future Nuxt v5 breaking changes. ### Source excerpt Nuxt 4.2 is out - with experimental TypeScript plugin support, better error handling in development, abort control for data fetching, and more! ## Sharing Excess Uses Neon Database Branches for Development Environments DevFeed: [Sharing Excess Uses Neon Database Branches for Development Environments]() Original publisher: [Read original article]() Author: Taraneh Dohmer Published: 2025-10-23T17:49:17Z Content type: article Language: en Sources: [Blog -- Neon Docs]() Topics: [Database](), [Drizzle](), [Bun](), [React](), [Vite]() Tags: [bun](), [case-studies](), [database](), [drizzle](), [react](), [vite]() ### AI overview This case study describes how Sharing Excess, a nonprofit food-rescue organization, uses Neon database branches for production, staging, and per-developer environments. Its three-person engineering team uses a Bun and TypeScript monorepo with React, Vite, Hono, Postgres, and Drizzle ORM. ### Source excerpt "For a small team, branching and scale-to-zero just make our lives markedly easier. We're able to use real data without risky scripts touching production, and we don't pay overnight for what we don't use." -- Ryan McHenry, Head of Technology, Sharing Excess What is Sharing Excess?... ## How We Built the Turso Shell in the Browser DevFeed: [How We Built the Turso Shell in the Browser]() Original publisher: [Read original article]() Author: Jamie Barton Published: 2025-10-14T00:00:00Z Content type: article Language: en Sources: [Turso Blog]() Topics: [Turso](), [SQLite](), [WebAssembly](), [Vite](), [SQL](), [Local-First](), [React](), [TypeScript](), [Tailwind CSS](), [Web Development]() Tags: [local-first](), [offline](), [react](), [sql](), [sqlite](), [sync](), [tailwind-css](), [turso](), [typescript](), [vite](), [webassembly]() ### AI overview This article explains how to build the Turso Shell, a full SQLite shell that runs entirely in the browser with Turso's WebAssembly build, Vite, OPFS storage, React, and TypeScript. It covers WASM loading, required COOP and COEP headers, database initialization, a SQL query interface, and upgrading the textarea to a syntax-highlighted code editor. The result is a local-first, offline-capable application that can operate without a backend and synchronize when needed. ### Source excerpt Build a full SQLite shell that runs entirely in the browser using Turso's WebAssembly build, OPFS storage, and Vite. No backend, no server required. [Next page]()