{"slug": "inertia-js", "name": "Inertia.js", "category": "dev-libs", "category_name": "Libraries and frameworks", "description": "", "recommenders": 4, "commenters": 4, "warners": 0, "score": 3.865, "rising": 3.67, "first": "2025-12-11", "latest": "2026-10-02", "why": "It\u2019s the best of both worlds. We use it to bridge svelte with Laravel at work and I couldn\u2019t be happier about this stack.", "why_is_quote": true, "has_verdict": false, "sentiment": {"recommend": 5, "neutral": 0, "compare": 0, "warn": 0}, "spark": [0, 1, 0, 0, 0, 0, 0, 0, 0, 2, 0, 2], "listed": true, "loved": [], "caveat": "", "short_quote": "It\u2019s the best of both worlds. We use it to bridge svelte with Laravel at work and I couldn\u2019t be happier about this stack.", "icon": true, "domain": "inertiajs.com", "github_repo": null, "official_url": "https://inertiajs.com", "pricing": "", "aliases": ["Inertia.js", "InertiaJS"], "verdict": null, "praise": [{"label": "", "summary": "", "quotes": [{"id": 798984496, "item_id": 49936531, "url": "https://news.ycombinator.com/item?id=49936531", "by": "0xblinq", "date": "2026-10-02", "stance": "recommend", "quote": "It\u2019s the best of both worlds. We use it to bridge svelte with Laravel at work and I couldn\u2019t be happier about this stack.", "excerpt": "Check inertia.js. It\u2019s the best of both worlds. We use it to bridge svelte with Laravel at work and I couldn\u2019t be happier about this stack.", "context": "uses it at work", "use_case": "bridge Svelte with Laravel", "switched_from": "", "story": "SvelteKit 3"}, {"id": 798860004, "item_id": 49928750, "url": "https://news.ycombinator.com/item?id=49928750", "by": "brachkow", "date": "2026-10-02", "stance": "recommend", "quote": "you can do SSR of any complexity in Vue + any backend you have", "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": "SSR with Vue", "switched_from": "", "story": "SvelteKit 3"}, {"id": 788482704, "item_id": 49280169, "url": "https://news.ycombinator.com/item?id=49280169", "by": "felixding", "date": "2026-08-12", "stance": "recommend", "quote": "Then I found Inertia.js and never looked back.", "excerpt": "I used all of them in various projects: \"traditional\" Ajax-based SPAs, HTML over WebSockets/SSE, etc. Then I found Inertia.js and never looked back. With Inertia.js, you get the real feel of an SPA without the complexity of maintaining APIs just for the frontend. You can even make some pages plain HTML (like the homepage, legal pages, etc.), while making pages that require reactivity SPAs.", "context": "", "use_case": "SPA feel without maintaining APIs", "switched_from": "", "story": "HTML over WebSockets: real-time SPAs with barely any JavaScript"}, {"id": 788432242, "item_id": 49277015, "url": "https://news.ycombinator.com/item?id=49277015", "by": "aitchnyu", "date": "2026-08-12", "stance": "recommend", "quote": "I use Django Ninja, Zod, InertiaJS+Vue", "excerpt": "I like the Vue/React/Svelte model of the DOM being a function of the data. For example, in a shopping cart, I add two chocolates, the number against the chocolate, the count at top and a banner encouraging me to reach X total all center around a data structure. I use Django Ninja, Zod, InertiaJS+Vue and its as easy as using Django's templating engine, but static typing ensures my view doesnt emit unrepresentable data", "context": "", "use_case": "connecting backend to frontend", "switched_from": "", "story": "HTML over WebSockets: real-time SPAs with barely any JavaScript"}, {"id": 739855936, "item_id": 46240996, "url": "https://news.ycombinator.com/item?id=46240996", "by": "0xblinq", "date": "2025-12-11", "stance": "recommend", "quote": "I can't recommend it enough.", "excerpt": "This is why I'm a big advocate of Inertia.js [1]. For me it's the right balance of using \"serious\" batteries included traditional MVC backends like Laravel, Rails, Adonis, Django, etc... and modern component based frontend tools like React, Vue, Svelte, etc. Responsibilities are clear, working in it is easy, and every single time I used it feels like you're using the right tool for each task. I can't recommend it eno", "context": "", "use_case": "connecting MVC backends to frontend frameworks", "switched_from": "", "story": "Denial of service and source code exposure in React Server Components"}]}], "caveats": [], "who": [{"by": "0xblinq", "context": "uses it at work", "url": "https://news.ycombinator.com/item?id=49936531", "date": "2026-10-02"}, {"by": "brachkow", "context": "has used both Svelte and Vue", "url": "https://news.ycombinator.com/item?id=49928750", "date": "2026-10-02"}], "tags": [], "use_cases": ["bridge svelte with laravel", "ssr with vue", "spa feel without maintaining apis", "connecting backend to frontend", "connecting mvc backends to frontend frameworks"], "compared": [{"slug": "vue", "name": "Vue", "co": 2, "switched_from": 0, "switched_to": 0}, {"slug": "sveltekit", "name": "SvelteKit", "co": 2, "switched_from": 0, "switched_to": 0}, {"slug": "svelte", "name": "Svelte", "co": 2, "switched_from": 0, "switched_to": 0}, {"slug": "react", "name": "React", "co": 2, "switched_from": 0, "switched_to": 0}], "makers": [], "threads": [{"url": "https://news.ycombinator.com/item?id=49926536", "title": "SvelteKit 3", "mentions": 2}, {"url": "https://news.ycombinator.com/item?id=49275335", "title": "HTML over WebSockets: real-time SPAs with barely any JavaScript", "mentions": 2}, {"url": "https://news.ycombinator.com/item?id=46236924", "title": "Denial of service and source code exposure in React Server Components", "mentions": 1}], "sentiment_by_month": {"2025-11": {}, "2025-12": {"recommend": 1}, "2026-01": {}, "2026-02": {}, "2026-03": {}, "2026-04": {}, "2026-05": {}, "2026-06": {}, "2026-07": {}, "2026-08": {"recommend": 2}, "2026-09": {}, "2026-10": {"recommend": 2}}, "quotes": [{"id": 798984496, "item_id": 49936531, "url": "https://news.ycombinator.com/item?id=49936531", "by": "0xblinq", "date": "2026-10-02", "stance": "recommend", "quote": "It\u2019s the best of both worlds. We use it to bridge svelte with Laravel at work and I couldn\u2019t be happier about this stack.", "excerpt": "Check inertia.js. It\u2019s the best of both worlds. We use it to bridge svelte with Laravel at work and I couldn\u2019t be happier about this stack.", "context": "uses it at work", "use_case": "bridge Svelte with Laravel", "switched_from": "", "story": "SvelteKit 3"}, {"id": 798860004, "item_id": 49928750, "url": "https://news.ycombinator.com/item?id=49928750", "by": "brachkow", "date": "2026-10-02", "stance": "recommend", "quote": "you can do SSR of any complexity in Vue + any backend you have", "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": "SSR with Vue", "switched_from": "", "story": "SvelteKit 3"}, {"id": 788482704, "item_id": 49280169, "url": "https://news.ycombinator.com/item?id=49280169", "by": "felixding", "date": "2026-08-12", "stance": "recommend", "quote": "Then I found Inertia.js and never looked back.", "excerpt": "I used all of them in various projects: \"traditional\" Ajax-based SPAs, HTML over WebSockets/SSE, etc. Then I found Inertia.js and never looked back. With Inertia.js, you get the real feel of an SPA without the complexity of maintaining APIs just for the frontend. You can even make some pages plain HTML (like the homepage, legal pages, etc.), while making pages that require reactivity SPAs.", "context": "", "use_case": "SPA feel without maintaining APIs", "switched_from": "", "story": "HTML over WebSockets: real-time SPAs with barely any JavaScript"}, {"id": 788432242, "item_id": 49277015, "url": "https://news.ycombinator.com/item?id=49277015", "by": "aitchnyu", "date": "2026-08-12", "stance": "recommend", "quote": "I use Django Ninja, Zod, InertiaJS+Vue", "excerpt": "I like the Vue/React/Svelte model of the DOM being a function of the data. For example, in a shopping cart, I add two chocolates, the number against the chocolate, the count at top and a banner encouraging me to reach X total all center around a data structure. I use Django Ninja, Zod, InertiaJS+Vue and its as easy as using Django's templating engine, but static typing ensures my view doesnt emit unrepresentable data", "context": "", "use_case": "connecting backend to frontend", "switched_from": "", "story": "HTML over WebSockets: real-time SPAs with barely any JavaScript"}, {"id": 739855936, "item_id": 46240996, "url": "https://news.ycombinator.com/item?id=46240996", "by": "0xblinq", "date": "2025-12-11", "stance": "recommend", "quote": "I can't recommend it enough.", "excerpt": "This is why I'm a big advocate of Inertia.js [1]. For me it's the right balance of using \"serious\" batteries included traditional MVC backends like Laravel, Rails, Adonis, Django, etc... and modern component based frontend tools like React, Vue, Svelte, etc. Responsibilities are clear, working in it is easy, and every single time I used it feels like you're using the right tool for each task. I can't recommend it eno", "context": "", "use_case": "connecting MVC backends to frontend frameworks", "switched_from": "", "story": "Denial of service and source code exposure in React Server Components"}]}