SvelteKit 3 takes on Next.js with a radical RPC overhaul — server logic inside components

The third major version of SvelteKit has been released, positioning itself as a direct competitor to Next.js by introducing a radically reimagined approach to Remote Procedure Calls (RPC). Instead of relying on separate API routes, SvelteKit 3 allows developers to embed server-side logic directly within Svelte components, eliminating boilerplate code and simplifying data flow between client and server.

The new RPC mechanism lets developers call server functions as if they were local, with automatic type handling and serialization. This lowers the entry barrier for newcomers and speeds up development for typical web applications. In contrast to Next.js, which often requires dedicated API routes or server actions for backend interaction, SvelteKit 3 consolidates logic into a single component file, making the codebase more intuitive and maintainable.

Beyond RPC, SvelteKit 3 introduces improved streaming support for dynamic content, which is critical for applications with large amounts of real-time data. The framework also features tighter integration with modern build tools and optimized module loading for faster startup times.

The update is positioned as a response to the growing complexity of Next.js, especially with the introduction of React Server Components. SvelteKit 3 emphasizes simplicity and performance while retaining flexibility for large-scale projects. The release is available now via npm, and early benchmarks suggest significant reductions in both code size and development time compared to previous versions.

The move is seen as a direct challenge to the dominance of Next.js in the React ecosystem, offering a simpler alternative for teams looking to build full-stack applications without the overhead of managing separate API layers. With SvelteKit 3, the Svelte team aims to prove that a component-based RPC model can be both powerful and developer-friendly.