FeatureFuel
1

Use SvelteKit Instead of Next.js

Source: supabase/supabase#49855 · opened by @suprabhaat
Summary I propose that we use SvelteKit instead of Next.js for the frontend. The goal is not to choose a framework based on popularity, but to choose the technology that gives us the best combination of performance, simplicity, maintainability, developer experience, and long-term flexibility. For this project, SvelteKit is a better fit because it provides the capabilities we need without requiring as much framework/runtime complexity. Why SvelteKit / Svelte ? 1. Less JavaScript shipped to the client Svelte takes a compiler-first approach. Instead of shipping a large framework runtime and having the browser interpret component behavior at runtime, much of the work is performed during the build. This can result in: • Smaller client-side JavaScript • Less runtime overhead • Faster page startup • Better performance on servers • Less work for the browser 2. Simpler components Svelte components are generally much more …

No pledges yet. Be the first to back this.

Make a pledge

Pledge your monetary support if this feature is added.

$

Comments

No comments yet.

Replying to

Add a comment

What do you think about this feature request?


Similar requests