Turbopack Error: failed to create whole tree

[Anwarul801]

Turbopack version: da605e0c
Next.js version: 0.0.0

Error message:

failed to create whole tree

[Wadan3]

Hi,

This looks like an internal Turbopack error, especially because the message is only:

failed to create whole tree

One thing I noticed is that the Next.js version is showing as 0.0.0, which looks unusual. I would first check if the correct Next.js version is installed:

npm list next

You can also try cleaning the project and running it again:

rm -rf .next
rm -rf node_modules
npm install
npm run dev

If you are using Turbopack, try running without it to confirm if the issue is only related to Turbopack:

next dev

If it works without Turbopack but fails with Turbopack, then it is probably a Turbopack bug. In that case, sharing a small reproduction repo would help the maintainers debug it.

Hope this helps.

[Jayanth0124]

I ran into the same issue:

Turbopack version: da605e0c
Next.js version: 0.0.0

Error:
failed to create whole tree

A few things helped narrow it down:

Things to Check

1. Clear the .next cache:

rm -rf .next

or on Windows:

rmdir /s /q .next

2. Reinstall dependencies:

rm -rf node_modules package-lock.json
npm install

3. Verify the Next.js installation:

npm list next

The reported version should be something like:

next@15.x.x

Seeing:

Next.js version: 0.0.0

looks suspicious and may indicate a corrupted or improperly resolved Next.js installation.

4. Try running without Turbopack:

npx next dev

or

npm run dev -- --no-turbo

If the app starts normally, the issue is likely Turbopack-specific.

5. Check for:

• Circular imports
• Invalid route files
• Missing layout.tsx
• Missing page.tsx
• Incorrect dynamic route implementations

Additional Information

The error message itself is quite generic. The most useful information would be:

• Full stack trace
• Next.js version from package.json
• Whether the project uses the App Router or Pages Router
• Any recent file or route changes before the error started occurring

The Next.js version: 0.0.0 output stands out as the most likely clue and is worth investigating first.