Dinou docs

⏏️ Eject Dinou

If you need full control over the internal configuration or build logic, you can "eject" the framework.

# Using npm script
npm run eject

# Or using the CLI directly
npx dinou eject

What Happens When You Eject?

Ejection Process

Copies the entire Dinou core into a dinou/ folder in your project root
Allows direct modification of build scripts, server logic, and configuration
Gives you complete freedom to customize the framework

When to Consider Ejecting

Ejection Use Cases

Need to modify the internal bundling process
Require custom server middleware or routing logic
Want to add support for additional file types or build features
Debugging deep framework issues

Ejection in the AI Era (Vibe-Coding)

In the era of AI coding agents (such as Cursor, Gemini Antigravity, or Copilot Workspace) and the "Vibe-Coding" workflow, the ability to eject the framework core transforms how you customize your application:

Empowering Your AI Co-Pilot

Traditional frameworks are hidden inside node_modules/ as pre-compiled black boxes. Because AI agents cannot inspect, debug, or modify them directly, they have to work around the framework's limitations.

By running npm run eject, the entire Dinou core is exposed in plain, readable source code inside dinou/core/:

Instant Context: AI agents can read and understand the entire routing, build, and server pipeline in seconds.
Seamless Modifications: Your AI assistant can directly implement custom middleware, extend asset compilation, or modify parallel route slots resolution directly within the framework core.
Zero Constraints: The boundary between "application code" and "framework code" is eliminated, enabling fluid and efficient full-stack vibe-coding.