{"slug": "nuxt", "name": "Nuxt", "category": "dev-libs", "category_name": "Libraries and frameworks", "description": "Open-source Vue framework for building server-rendered and full-stack web applications.", "recommenders": 6, "commenters": 8, "warners": 2, "score": 3.303, "rising": -0.64, "first": "2025-12-15", "latest": "2026-10-06", "why": "HN commenters like Nuxt for its ecosystem packages and templates such as Nuxt UI, and as a Vue-based alternative to React and Next.js, including for one-person teams.", "why_is_quote": false, "has_verdict": true, "sentiment": {"recommend": 6, "neutral": 0, "compare": 0, "warn": 2}, "spark": [0, 2, 1, 0, 0, 1, 0, 0, 1, 0, 0, 1], "listed": true, "loved": ["Ecosystem", "Next.js alternative"], "caveat": "Foot guns", "short_quote": "Nuxt (Vue) instead of Next.js (React). I chose this even though I'm new to vue cause I saw the open source components and templates here [2]", "icon": true, "domain": "nuxt.com", "github_repo": null, "official_url": "https://nuxt.com", "pricing": "open source", "aliases": ["Nuxt"], "verdict": [{"text": "HN commenters like Nuxt for its ecosystem packages and templates such as Nuxt UI,", "cites": [{"id": 799611056, "item_id": 49975691, "url": "https://news.ycombinator.com/item?id=49975691", "by": "petr25102018", "date": "2026-10-06", "stance": "recommend", "quote": "found it actually awesome for one person team", "excerpt": "I didn't like Nuxt in the past, but I switched to it recently from Django and found it actually awesome for one person team. I am constantly amazed by its ecosystem packages like NuxtUI or NuxtSEO.", "context": "one person team", "use_case": "web app development", "switched_from": "Django", "story": "Nuxt 4.6"}, {"id": 782237185, "item_id": 48889824, "url": "https://news.ycombinator.com/item?id=48889824", "by": "remy__", "date": "2026-07-13", "stance": "recommend", "quote": "an excuse to work with Nuxt / Nuxt UI as I loved the development of those projects", "excerpt": "I was kind of disappointed at our HOA management system so I made my own: https://hoamy.app Started of manually, later stages I used AI for implementing similar pages, and then for reviewing my own code. (It was also an excuse to work with Nuxt / Nuxt UI as I loved the development of those projects and wanted to implement something with it.)", "context": "", "use_case": "building web app", "switched_from": "", "story": "Ask HN: What Are You Working On? (July 2026)"}, {"id": 741204210, "item_id": 46325263, "url": "https://news.ycombinator.com/item?id=46325263", "by": "zaphodias", "date": "2025-12-19", "stance": "recommend", "quote": "Nuxt (Vue) instead of Next.js (React). I chose this even though I'm new to vue cause I saw the open source components and templates here [2]", "excerpt": "This is great - thanks for sharing. I am actually building something very similar myself as I started building a couple SaaS and though it would be nice to extract the common pieces in a template. My stack is similar, with a few differences: - Go backend with sqlc, but using ConnectRPC[1]. I chose this as it allows me to define a proper API scheme and generate a decent-quality Typescript client. - Nuxt (Vue) instead ", "context": "building SaaS products", "use_case": "SaaS frontend", "switched_from": "", "story": "Show HN: I open-sourced my Go and Next B2B SaaS Starter (deploy anywhere, MIT)"}]}, {"text": " and as a Vue-based alternative to React and Next.js, including for one-person teams.", "cites": [{"id": 763844881, "item_id": 47740305, "url": "https://news.ycombinator.com/item?id=47740305", "by": "fny", "date": "2026-04-12", "stance": "recommend", "quote": "I switched from React/Next to Vue/Nuxt.", "excerpt": "Aside from the obvious \"AI can't see\" criticism, AI sucks at frontend because frontend sucks. Why does frontend suck? Churn. To quote the article: 1. \"It trained on ancient garbage\" which is the by product of massive churn and this attitude leads to even more churn 2. \"It doesn't know WHY we do things\" because we don't either... even the paradigms used in frontend dev have needlessly churned My fix? I switched from R", "context": "", "use_case": "frontend development", "switched_from": "Next.js", "story": "Why AI Sucks at Front End"}, {"id": 741204210, "item_id": 46325263, "url": "https://news.ycombinator.com/item?id=46325263", "by": "zaphodias", "date": "2025-12-19", "stance": "recommend", "quote": "Nuxt (Vue) instead of Next.js (React). I chose this even though I'm new to vue cause I saw the open source components and templates here [2]", "excerpt": "This is great - thanks for sharing. I am actually building something very similar myself as I started building a couple SaaS and though it would be nice to extract the common pieces in a template. My stack is similar, with a few differences: - Go backend with sqlc, but using ConnectRPC[1]. I chose this as it allows me to define a proper API scheme and generate a decent-quality Typescript client. - Nuxt (Vue) instead ", "context": "building SaaS products", "use_case": "SaaS frontend", "switched_from": "", "story": "Show HN: I open-sourced my Go and Next B2B SaaS Starter (deploy anywhere, MIT)"}, {"id": 740387568, "item_id": 46274223, "url": "https://news.ycombinator.com/item?id=46274223", "by": "seergiue", "date": "2025-12-15", "stance": "recommend", "quote": "paired with the reactivity of the new Nuxt 4.", "excerpt": "Hi HN, I\u2019ve been building SaaS products for a while, and I started getting \"setup fatigue.\" Every time I validated a new idea, I lost the first two weeks just configuring Docker, wrestling with Stripe webhooks, and setting up Auth flows. The market defaults to Next.js for everything right now. While Next is great, I found myself missing the structure of a dedicated backend framework. I wanted the type-safety and \"bat", "context": "builds SaaS products", "use_case": "SaaS frontend", "switched_from": "", "story": "Show HN: A SaaS starter kit built with Nuxt 4 and AdonisJS v6"}, {"id": 799611056, "item_id": 49975691, "url": "https://news.ycombinator.com/item?id=49975691", "by": "petr25102018", "date": "2026-10-06", "stance": "recommend", "quote": "found it actually awesome for one person team", "excerpt": "I didn't like Nuxt in the past, but I switched to it recently from Django and found it actually awesome for one person team. I am constantly amazed by its ecosystem packages like NuxtUI or NuxtSEO.", "context": "one person team", "use_case": "web app development", "switched_from": "Django", "story": "Nuxt 4.6"}]}, {"text": " Critics say the framework is full of foot guns and reinvented wheels,", "cites": [{"id": 798860002, "item_id": 49928750, "url": "https://news.ycombinator.com/item?id=49928750", "by": "brachkow", "date": "2026-10-02", "stance": "warn", "quote": "Nuxt is, to put it mildly... not a good framework.", "excerpt": "I do. I wrote on this extensively there \u2013 https://www.brachkow.com/notes/my-experience-with-svelte/ In short: 1. Svelte is a good framework, but most of the DX praise comes from React folk. In my experience, Svelte is less polished and less comfortable to work with than Vue. 2. The biggest problem with Vue is that your choice of SSR frameworks is limited to Nuxt, and Nuxt is, to put it mildly... not a good framework.", "context": "has used both Svelte and Vue", "use_case": "Vue SSR", "switched_from": "", "story": "SvelteKit 3"}]}, {"text": " and some cite chaos from the Nuxt team, moving to plain Vite or SvelteKit instead.", "cites": [{"id": 799606769, "item_id": 49975423, "url": "https://news.ycombinator.com/item?id=49975423", "by": "popalchemist", "date": "2026-10-06", "stance": "warn", "quote": "Got sick of Nuxt and the Nuxt Team's chaos years ago.", "excerpt": "I love Vue. Got sick of Nuxt and the Nuxt Team's chaos years ago. Went pure vite. Never missed it once.", "context": "", "use_case": "Vue development", "switched_from": "", "story": "Nuxt 4.6"}, {"id": 798860002, "item_id": 49928750, "url": "https://news.ycombinator.com/item?id=49928750", "by": "brachkow", "date": "2026-10-02", "stance": "warn", "quote": "Nuxt is, to put it mildly... not a good framework.", "excerpt": "I do. I wrote on this extensively there \u2013 https://www.brachkow.com/notes/my-experience-with-svelte/ In short: 1. Svelte is a good framework, but most of the DX praise comes from React folk. In my experience, Svelte is less polished and less comfortable to work with than Vue. 2. The biggest problem with Vue is that your choice of SSR frameworks is limited to Nuxt, and Nuxt is, to put it mildly... not a good framework.", "context": "has used both Svelte and Vue", "use_case": "Vue SSR", "switched_from": "", "story": "SvelteKit 3"}]}], "praise": [{"label": "Ecosystem", "summary": "Packages and templates like Nuxt UI, NuxtSEO and the dashboard template draw people in.", "quotes": [{"id": 799611056, "item_id": 49975691, "url": "https://news.ycombinator.com/item?id=49975691", "by": "petr25102018", "date": "2026-10-06", "stance": "recommend", "quote": "found it actually awesome for one person team", "excerpt": "I didn't like Nuxt in the past, but I switched to it recently from Django and found it actually awesome for one person team. I am constantly amazed by its ecosystem packages like NuxtUI or NuxtSEO.", "context": "one person team", "use_case": "web app development", "switched_from": "Django", "story": "Nuxt 4.6"}, {"id": 782237185, "item_id": 48889824, "url": "https://news.ycombinator.com/item?id=48889824", "by": "remy__", "date": "2026-07-13", "stance": "recommend", "quote": "an excuse to work with Nuxt / Nuxt UI as I loved the development of those projects", "excerpt": "I was kind of disappointed at our HOA management system so I made my own: https://hoamy.app Started of manually, later stages I used AI for implementing similar pages, and then for reviewing my own code. (It was also an excuse to work with Nuxt / Nuxt UI as I loved the development of those projects and wanted to implement something with it.)", "context": "", "use_case": "building web app", "switched_from": "", "story": "Ask HN: What Are You Working On? (July 2026)"}, {"id": 741204210, "item_id": 46325263, "url": "https://news.ycombinator.com/item?id=46325263", "by": "zaphodias", "date": "2025-12-19", "stance": "recommend", "quote": "Nuxt (Vue) instead of Next.js (React). I chose this even though I'm new to vue cause I saw the open source components and templates here [2]", "excerpt": "This is great - thanks for sharing. I am actually building something very similar myself as I started building a couple SaaS and though it would be nice to extract the common pieces in a template. My stack is similar, with a few differences: - Go backend with sqlc, but using ConnectRPC[1]. I chose this as it allows me to define a proper API scheme and generate a decent-quality Typescript client. - Nuxt (Vue) instead ", "context": "building SaaS products", "use_case": "SaaS frontend", "switched_from": "", "story": "Show HN: I open-sourced my Go and Next B2B SaaS Starter (deploy anywhere, MIT)"}]}, {"label": "Next.js alternative", "summary": "Chosen over React/Next.js by developers wanting a Vue-based stack.", "quotes": [{"id": 763844881, "item_id": 47740305, "url": "https://news.ycombinator.com/item?id=47740305", "by": "fny", "date": "2026-04-12", "stance": "recommend", "quote": "I switched from React/Next to Vue/Nuxt.", "excerpt": "Aside from the obvious \"AI can't see\" criticism, AI sucks at frontend because frontend sucks. Why does frontend suck? Churn. To quote the article: 1. \"It trained on ancient garbage\" which is the by product of massive churn and this attitude leads to even more churn 2. \"It doesn't know WHY we do things\" because we don't either... even the paradigms used in frontend dev have needlessly churned My fix? I switched from R", "context": "", "use_case": "frontend development", "switched_from": "Next.js", "story": "Why AI Sucks at Front End"}, {"id": 741204210, "item_id": 46325263, "url": "https://news.ycombinator.com/item?id=46325263", "by": "zaphodias", "date": "2025-12-19", "stance": "recommend", "quote": "Nuxt (Vue) instead of Next.js (React). I chose this even though I'm new to vue cause I saw the open source components and templates here [2]", "excerpt": "This is great - thanks for sharing. I am actually building something very similar myself as I started building a couple SaaS and though it would be nice to extract the common pieces in a template. My stack is similar, with a few differences: - Go backend with sqlc, but using ConnectRPC[1]. I chose this as it allows me to define a proper API scheme and generate a decent-quality Typescript client. - Nuxt (Vue) instead ", "context": "building SaaS products", "use_case": "SaaS frontend", "switched_from": "", "story": "Show HN: I open-sourced my Go and Next B2B SaaS Starter (deploy anywhere, MIT)"}, {"id": 740387568, "item_id": 46274223, "url": "https://news.ycombinator.com/item?id=46274223", "by": "seergiue", "date": "2025-12-15", "stance": "recommend", "quote": "paired with the reactivity of the new Nuxt 4.", "excerpt": "Hi HN, I\u2019ve been building SaaS products for a while, and I started getting \"setup fatigue.\" Every time I validated a new idea, I lost the first two weeks just configuring Docker, wrestling with Stripe webhooks, and setting up Auth flows. The market defaults to Next.js for everything right now. While Next is great, I found myself missing the structure of a dedicated backend framework. I wanted the type-safety and \"bat", "context": "builds SaaS products", "use_case": "SaaS frontend", "switched_from": "", "story": "Show HN: A SaaS starter kit built with Nuxt 4 and AdonisJS v6"}]}, {"label": "Solo development", "summary": "One former Django user found it awesome for a one-person team.", "quotes": [{"id": 799611056, "item_id": 49975691, "url": "https://news.ycombinator.com/item?id=49975691", "by": "petr25102018", "date": "2026-10-06", "stance": "recommend", "quote": "found it actually awesome for one person team", "excerpt": "I didn't like Nuxt in the past, but I switched to it recently from Django and found it actually awesome for one person team. I am constantly amazed by its ecosystem packages like NuxtUI or NuxtSEO.", "context": "one person team", "use_case": "web app development", "switched_from": "Django", "story": "Nuxt 4.6"}]}, {"label": "Reactivity", "summary": "The reactivity of Nuxt 4 is cited as a reason to pair it with a backend framework.", "quotes": [{"id": 740387568, "item_id": 46274223, "url": "https://news.ycombinator.com/item?id=46274223", "by": "seergiue", "date": "2025-12-15", "stance": "recommend", "quote": "paired with the reactivity of the new Nuxt 4.", "excerpt": "Hi HN, I\u2019ve been building SaaS products for a while, and I started getting \"setup fatigue.\" Every time I validated a new idea, I lost the first two weeks just configuring Docker, wrestling with Stripe webhooks, and setting up Auth flows. The market defaults to Next.js for everything right now. While Next is great, I found myself missing the structure of a dedicated backend framework. I wanted the type-safety and \"bat", "context": "builds SaaS products", "use_case": "SaaS frontend", "switched_from": "", "story": "Show HN: A SaaS starter kit built with Nuxt 4 and AdonisJS v6"}]}], "caveats": [{"label": "Foot guns", "summary": "One commenter calls it full of reinventing the wheel, ambiguity and foot guns, and regretted every Nuxt project.", "quotes": [{"id": 798860002, "item_id": 49928750, "url": "https://news.ycombinator.com/item?id=49928750", "by": "brachkow", "date": "2026-10-02", "stance": "warn", "quote": "Nuxt is, to put it mildly... not a good framework.", "excerpt": "I do. I wrote on this extensively there \u2013 https://www.brachkow.com/notes/my-experience-with-svelte/ In short: 1. Svelte is a good framework, but most of the DX praise comes from React folk. In my experience, Svelte is less polished and less comfortable to work with than Vue. 2. The biggest problem with Vue is that your choice of SSR frameworks is limited to Nuxt, and Nuxt is, to put it mildly... not a good framework.", "context": "has used both Svelte and Vue", "use_case": "Vue SSR", "switched_from": "", "story": "SvelteKit 3"}]}, {"label": "Team chaos", "summary": "A Vue fan got sick of the Nuxt team's chaos and switched to pure Vite.", "quotes": [{"id": 799606769, "item_id": 49975423, "url": "https://news.ycombinator.com/item?id=49975423", "by": "popalchemist", "date": "2026-10-06", "stance": "warn", "quote": "Got sick of Nuxt and the Nuxt Team's chaos years ago.", "excerpt": "I love Vue. Got sick of Nuxt and the Nuxt Team's chaos years ago. Went pure vite. Never missed it once.", "context": "", "use_case": "Vue development", "switched_from": "", "story": "Nuxt 4.6"}]}, {"label": "Limited SSR choice", "summary": "Nuxt is described as effectively the only SSR framework option for Vue.", "quotes": [{"id": 798860002, "item_id": 49928750, "url": "https://news.ycombinator.com/item?id=49928750", "by": "brachkow", "date": "2026-10-02", "stance": "warn", "quote": "Nuxt is, to put it mildly... not a good framework.", "excerpt": "I do. I wrote on this extensively there \u2013 https://www.brachkow.com/notes/my-experience-with-svelte/ In short: 1. Svelte is a good framework, but most of the DX praise comes from React folk. In my experience, Svelte is less polished and less comfortable to work with than Vue. 2. The biggest problem with Vue is that your choice of SSR frameworks is limited to Nuxt, and Nuxt is, to put it mildly... not a good framework.", "context": "has used both Svelte and Vue", "use_case": "Vue SSR", "switched_from": "", "story": "SvelteKit 3"}]}], "who": [{"by": "petr25102018", "context": "one person team", "url": "https://news.ycombinator.com/item?id=49975691", "date": "2026-10-06"}, {"by": "neciudan", "context": "podcast host", "url": "https://news.ycombinator.com/item?id=46709580", "date": "2026-01-21"}, {"by": "zaphodias", "context": "building SaaS products", "url": "https://news.ycombinator.com/item?id=46325263", "date": "2025-12-19"}, {"by": "seergiue", "context": "builds SaaS products", "url": "https://news.ycombinator.com/item?id=46274223", "date": "2025-12-15"}], "tags": ["for Vue developers", "for solo devs", "for SaaS products"], "use_cases": ["saas frontend", "web app development", "vue development", "vue ssr", "building web app", "frontend development"], "compared": [{"slug": "next-js", "name": "Next.js", "co": 4, "switched_from": 1, "switched_to": 0}, {"slug": "django", "name": "Django", "co": 2, "switched_from": 1, "switched_to": 0}, {"slug": "sveltekit", "name": "SvelteKit", "co": 1, "switched_from": 0, "switched_to": 1}, {"slug": "vite", "name": "Vite", "co": 1, "switched_from": 0, "switched_to": 1}, {"slug": "react", "name": "React", "co": 2, "switched_from": 0, "switched_to": 0}, {"slug": "vue", "name": "Vue", "co": 2, "switched_from": 0, "switched_to": 0}], "makers": [], "threads": [{"url": "https://news.ycombinator.com/item?id=49975413", "title": "Nuxt 4.6", "mentions": 2}, {"url": "https://news.ycombinator.com/item?id=49926536", "title": "SvelteKit 3", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=48884984", "title": "Ask HN: What Are You Working On? (July 2026)", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=47738864", "title": "Why AI Sucks at Front End", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=46709579", "title": "Nuxt at Scale with Daniel Roe (Podcast Episode)", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=46324665", "title": "Show HN: I open-sourced my Go and Next B2B SaaS Starter (deploy anywhere, MIT)", "mentions": 1}], "sentiment_by_month": {"2025-11": {}, "2025-12": {"recommend": 2}, "2026-01": {"recommend": 1}, "2026-02": {}, "2026-03": {}, "2026-04": {"recommend": 1}, "2026-05": {}, "2026-06": {}, "2026-07": {"recommend": 1}, "2026-08": {}, "2026-09": {}, "2026-10": {"warn": 2, "recommend": 1}}, "quotes": [{"id": 799611056, "item_id": 49975691, "url": "https://news.ycombinator.com/item?id=49975691", "by": "petr25102018", "date": "2026-10-06", "stance": "recommend", "quote": "found it actually awesome for one person team", "excerpt": "I didn't like Nuxt in the past, but I switched to it recently from Django and found it actually awesome for one person team. I am constantly amazed by its ecosystem packages like NuxtUI or NuxtSEO.", "context": "one person team", "use_case": "web app development", "switched_from": "Django", "story": "Nuxt 4.6"}, {"id": 799606769, "item_id": 49975423, "url": "https://news.ycombinator.com/item?id=49975423", "by": "popalchemist", "date": "2026-10-06", "stance": "warn", "quote": "Got sick of Nuxt and the Nuxt Team's chaos years ago.", "excerpt": "I love Vue. Got sick of Nuxt and the Nuxt Team's chaos years ago. Went pure vite. Never missed it once.", "context": "", "use_case": "Vue development", "switched_from": "", "story": "Nuxt 4.6"}, {"id": 798860002, "item_id": 49928750, "url": "https://news.ycombinator.com/item?id=49928750", "by": "brachkow", "date": "2026-10-02", "stance": "warn", "quote": "Nuxt is, to put it mildly... not a good framework.", "excerpt": "I do. I wrote on this extensively there \u2013 https://www.brachkow.com/notes/my-experience-with-svelte/ In short: 1. Svelte is a good framework, but most of the DX praise comes from React folk. In my experience, Svelte is less polished and less comfortable to work with than Vue. 2. The biggest problem with Vue is that your choice of SSR frameworks is limited to Nuxt, and Nuxt is, to put it mildly... not a good framework.", "context": "has used both Svelte and Vue", "use_case": "Vue SSR", "switched_from": "", "story": "SvelteKit 3"}, {"id": 782237185, "item_id": 48889824, "url": "https://news.ycombinator.com/item?id=48889824", "by": "remy__", "date": "2026-07-13", "stance": "recommend", "quote": "an excuse to work with Nuxt / Nuxt UI as I loved the development of those projects", "excerpt": "I was kind of disappointed at our HOA management system so I made my own: https://hoamy.app Started of manually, later stages I used AI for implementing similar pages, and then for reviewing my own code. (It was also an excuse to work with Nuxt / Nuxt UI as I loved the development of those projects and wanted to implement something with it.)", "context": "", "use_case": "building web app", "switched_from": "", "story": "Ask HN: What Are You Working On? (July 2026)"}, {"id": 763844881, "item_id": 47740305, "url": "https://news.ycombinator.com/item?id=47740305", "by": "fny", "date": "2026-04-12", "stance": "recommend", "quote": "I switched from React/Next to Vue/Nuxt.", "excerpt": "Aside from the obvious \"AI can't see\" criticism, AI sucks at frontend because frontend sucks. Why does frontend suck? Churn. To quote the article: 1. \"It trained on ancient garbage\" which is the by product of massive churn and this attitude leads to even more churn 2. \"It doesn't know WHY we do things\" because we don't either... even the paradigms used in frontend dev have needlessly churned My fix? I switched from R", "context": "", "use_case": "frontend development", "switched_from": "Next.js", "story": "Why AI Sucks at Front End"}, {"id": 747353280, "item_id": 46709580, "url": "https://news.ycombinator.com/item?id=46709580", "by": "neciudan", "date": "2026-01-21", "stance": "recommend", "quote": "Whether you're already building with Nuxt, considering it for a project, or just curious about framework design philosophy, thought this might be worth a listen.", "excerpt": "I just released an interview with Daniel Roe (Nuxt Core team lead at Vercel) and thought folks here might find it interesting. We talked about: *His journey into Vue* - Started in the Laravel world (shoutout to Laracasts) - Moved from WordPress to Laravel to Vue/Nuxt - Went from being a Nuxt user \u2192 contributor \u2192 core team lead *On building frameworks and DX* - Why being your own target audience makes you a better fra", "context": "podcast host", "use_case": "web framework", "switched_from": "", "story": "Nuxt at Scale with Daniel Roe (Podcast Episode)"}, {"id": 741204210, "item_id": 46325263, "url": "https://news.ycombinator.com/item?id=46325263", "by": "zaphodias", "date": "2025-12-19", "stance": "recommend", "quote": "Nuxt (Vue) instead of Next.js (React). I chose this even though I'm new to vue cause I saw the open source components and templates here [2]", "excerpt": "This is great - thanks for sharing. I am actually building something very similar myself as I started building a couple SaaS and though it would be nice to extract the common pieces in a template. My stack is similar, with a few differences: - Go backend with sqlc, but using ConnectRPC[1]. I chose this as it allows me to define a proper API scheme and generate a decent-quality Typescript client. - Nuxt (Vue) instead ", "context": "building SaaS products", "use_case": "SaaS frontend", "switched_from": "", "story": "Show HN: I open-sourced my Go and Next B2B SaaS Starter (deploy anywhere, MIT)"}, {"id": 740387568, "item_id": 46274223, "url": "https://news.ycombinator.com/item?id=46274223", "by": "seergiue", "date": "2025-12-15", "stance": "recommend", "quote": "paired with the reactivity of the new Nuxt 4.", "excerpt": "Hi HN, I\u2019ve been building SaaS products for a while, and I started getting \"setup fatigue.\" Every time I validated a new idea, I lost the first two weeks just configuring Docker, wrestling with Stripe webhooks, and setting up Auth flows. The market defaults to Next.js for everything right now. While Next is great, I found myself missing the structure of a dedicated backend framework. I wanted the type-safety and \"bat", "context": "builds SaaS products", "use_case": "SaaS frontend", "switched_from": "", "story": "Show HN: A SaaS starter kit built with Nuxt 4 and AdonisJS v6"}]}