Dinou docs

This reference map is designed to help you and your AI assistant quickly understand which files control different aspects of the Dinou framework.

📂 Overview & Tree Structure

Running the eject command copies the entire framework source code—including the web server, bundler scripts, client runtime, and core React Server Components engine—directly into the ./dinou/ folder at your project root. This grants you total ownership and control over how your pages are built, rendered, and served.

dinou/
├── constants.js            # Global environment settings
├── index.js                # Core package entry point (exports components & hooks)
├── index.mjs               # ESM entry point mapping for modern build imports
├── package.json            # Local dependency overrides for ejected script runners
├── server.js               # Entry point for the parent Node.js server
├── core/                   # ⚙️ Core RSC engine, router, and renderers (47 files)
│   ├── babel-esm-loader.js # Custom ESM loader thread for Babel compilation
│   ├── render-html.js      # Child process HTML renderer (Standard Client SSR)
│   ├── css-require-hook.js # PostCSS CSS Modules require loader
│   ├── client.jsx          # Client hydration entry point (Rollup/esbuild)
│   ├── client-webpack.jsx  # Client hydration entry point (Webpack config)
│   └── ...
├── esbuild/                # ⚡ esbuild compilation scripts
├── rollup/                 # 🔄 Rollup compilation configurations
└── webpack/                # 🕸️ Webpack bundler & hot-reload orchestrators

Empowering AI Pair Programming

With the entire framework code exposed inside ./dinou/, AI coding assistants (like Cursor, Gemini Antigravity, or Copilot) have full context of your fullstack execution path. They can help you write middleware, debug request states, or optimize asset caching directly inside these files.