NuxtN
Nuxt3w ago
6 replies
mika

Extremely long build times with nuxt build --extends docus (Nitro node-server, Windows)

Extremely long build times with nuxt build --extends docus (Nitro node-server, Windows)

Description


When building a Docus project with nuxt build --extends docus, the step “Building Nuxt Nitro server (preset: node-server, compatibility date: 2025-07-14) on Windows takes an extremely long time (around 45–60 minutes), even though the project itself is relatively small. This makes the build process practically unusable for local development and CI workflows.


Environment


- OS: Windows 11 Enterprise 23H2
- Node.js: 22.18.0
- Package manager: tried on bun, pnpm, npm
- Nuxt version: (from
package.json
, e.g. ^4.2.2)
- Docus version: (from
package.json
, e.g. latest)
- nuxt-studio: 1.0.0-beta.3
- Command: nuxt build --extends docus
- Nitro preset: node-server with compatibilityDate: '2025-07-14'


Steps to reproduce


1. Create a Docus-based documentation project (or use an existing Nuxt project that extends Docus and includes Studio).
2. Configure Nuxt to use Docus as a layer, for example via nuxt.config with extends: ['docus'] (or the Docus default setup).
3. On a Windows machine, run:
- npx nuxt build --extends docus
4. Observe the build output:
- The process stays for a very long time on
ℹ Building Nuxt Nitro server (preset: node-server, compatibility date: 2025-07-14) nitro 09:20:37
- Total build time is about 45–60 minutes.


Expected behavior


- The Nitro build step should complete within a few minutes at most on a typical Windows development machine.
- Build duration should be in line with usual Nuxt/Nitro projects (seconds to a few minutes, depending on project size), not close to an hour.


Actual behavior


- The step “Building Nuxt Nitro server (preset: node-server, compatibility date: 2025-07-14) runs for 45–60 minutes.
- During this time, the build appears to be “stuck” on this line, though it eventually finishes or may be aborted manually

Additional information / Debugging


- The issue occurs on Windows (also tried on wsl)
Was this page helpful?