Uploaded January 2023 | Updated September 2026, 3 weeks ago

---

In this video I summarize my findings from the "Choosing a Full Stack Framework" series. In the series I evaluated the ecosystem for SvelteKit, Nuxt 3, Remix and Next.js. I evaluated the project setup, configuration, tailwind setup, component library setup, auth library setup and built-in full stack type safety. We used Authjs with SvelteKit, @sidebase/nuxt-auth with Nuxt 3, remix-auth with Remix and next-auth with Next.js

This video was clipped from a live stream on twitch. Follow to watch live: twitch.tv/codinggarden

View the code for these apps here: github.com/CodingGarden/choosing-a-full-stack-framework

View the slide deck here: github.com/CodingGarden/choosing-a-full-stack-framework/tree/main/apps/findings

View the live streams where I tried each framework here: youtube.com/playlist?list=PLM_i0obccy3sbRnr6pq1ZIuuo9GaYP4yO

These full stack frameworks each have their own way of doing these things:

- Hybrid rendering (SPA vs SSR vs MPA vs SSG)
- Optimized bundling
- SEO
- File based routing
- API Functions / Data Loading
- Middlewares
- Environment configuration loading
- Image optimization

📩 Sign up for my mailing list: https://list.coding.garden/
💖 Donate: https://coding.garden/donate
😍 Pledge: https://coding.garden/pledge
💬 Discord: https://coding.garden/discord
🎉 Stickers: https://coding.garden/stickers
💻 Gear List: https://coding.garden/gear
🔎 Search for more Coding Garden videos here: https://coding.garden/videos
🗣 View the Coding Garden FAQ here: github.com/CodingGarden/faqs