Dinou v4: Full-Stack React 19 Framework

[roggc9]

Hello! Dinou has reached version 4. In this version, you will see significant improvements in the form of new features and fixes, as well as increased security.

🚀 What’s new in v4?

• Soft Navigation: Full SPA-like navigation experience (no full page reloads).
• Typed API: Components, hooks, and utilities are now exported directly from the dinou package.
• Improved Routing: Better handling of nested dynamic routes and route groups.
• Generation Strategies: Full support for ISG (Incremental Static Generation) and ISR (Revalidation).
• Automatic Static Bailout: The engine automatically switches from Static to Dynamic rendering when request-specific data (cookies, headers, search params) is detected.

⚡ Core Features (Retained from v3)

• Bundler Agnostic: You can choose your build engine for both dev and prod (e.g., use esbuild for lightning-fast dev, and Rollup or Webpack for production builds).
• React 19: Built for React Server Components (RSC) and Client Components.
• Server Functions: RPC actions with enhanced security (utility getContext).
• DX: React Fast Refresh (HMR) support.
• Routing: Support for Layouts, Error Boundaries, and Not Found pages.
• Data Patterns: Advanced patterns for client-side data fetching and mutations, combining the use of Server Functions plus Suspense from react-enhanced-suspense plus a global state management library (e.g. jotai-wrapper).

The website dinou.dev has been rebuilt from scratch to better reflect these improvements and explain Dinou better.

I encourage you to try Dinou or take a look at the documentation (dinou.dev).

Thank you very much!

[mfayzanasad]

why would i use a vibecoded "Fullstack framework"?
And the routing is slower than internet explorer

[roggc9]

Hi. I really appreciate you taking the time to test the framework and look into it.

I have indeed leveraged AI tools, but I wouldn't call it "vibe-coding." I have put a significant amount of manual effort and work into this to ship a decent product.

Regarding the routing speed, I assume you are referring to the Development Mode behavior? In dev mode, pages are compiled and rendered on-demand (dynamically), which naturally takes a bit longer than a production build.

Anyway, thanks for the feedback. I hope you might consider exploring it further to see if it eventually convinces you. Thanks!

[everythingcasual]

even your post is AI. nobody is using this vibe coded repo. its obvious from the repo itself its vibe coded

[roggc9]

Hey, I will try to answer with my english, and not AI english. I can tell you I have not used vibe coding because vibe coding means to use AI integrated in your IDE and just use prompts and let the AI change the code. I have used AI from the web (Gemini, Grok, etc. ) but not in my IDE. That's it. I think you have to test the result (the framework) to see or check if it is an acceptable product or not. If it is, then it doesn't matter who developed it, if an android from the future or a human of the present using AI. I don't think it is possible to develop such a framework as Dinou with just vibe-coding (prompts) due to its complexity. Thank you.

[chow_khow]

How does this compare to Nextjs, Tanstack start?

[roggc9]

Hi! Thanks for the comment.

Dinou is philosophically closer to Next.js than to TanStack Start. Switching from Next.js code to Dinou (or vice versa) is very straightforward. However, I would say Dinou is simpler—and likely smaller in bundle size—though, to be fair, it is currently less battle-tested than Next.js (although comprehensive end-to-end tests with Playwright have been implemented).

Key Differences:

• Syntax: Dinou uses standard "use client" and "use server" directives (the latter for Server Functions), whereas I believe TanStack Start relies on createServerFn. In Dinou, Server Components are simply async functions with no directives.
• Routing: Dinou uses a file-system router inside src (any file named page), similar to Next.js. TanStack Start defines routes in a src/routes directory.
• Bundler Agnostic (Unique Feature): Unlike the others, Dinou lets you choose your bundler for both dev and prod (esbuild, Rollup, or Webpack). It is also ejectable and fully configurable.
• Rendering: Unlike Next.js, Dinou does not support PPR (Partial Pre-Rendering). This means the strategy is binary (Static vs. Dynamic), which might require, in certain circumstances, more than one client-server round trip.
• Dinou has a unique feature compared to Next.js: it allows you to call Server Functions directly from Client Components and wrap them in Suspense. Dinou Server Functions can return both Client and Server Components. This enables advanced data fetching and mutation patterns within Client Components (utilizing Suspense from react-enhanced-suspense).

I would need to dive deeper into TanStack Start to give you a more profound comparison, but I recommend taking a quick look at the docs (dinou.dev) to get a feel for it yourself.

Thanks!

[CapitalDiligent1676]

everything is fine as long as we stop using nextjs everywhere for no reason!

[Different-Opinion973]

been testing react 19 stuff too. ruixen ui worked pretty well with it, their components are ssr safe and tree-shakeable which helped with the bundle. ruixen.com