Turbo pack eating all CPU | Hitting cpu

[mozaddedalfeshani]

Summary

Turbo pack is consuming all CPU resources and causing a CPU overload. This issue can be resolved by using the following package:

https://www.npmjs.com/package/nextcool

Additional information

No response

Example

No response

[wanhei1]

⚠️ Warning: The nextcool package linked above appears to be an unofficial workaround with unknown security implications. I'd recommend caution before installing it.

Legitimate Solutions for Turbopack CPU Issues

1. Limit Turbopack's worker threads

# Set thread limit before running dev server
export TURBOPACK_WORKER_THREADS=4  # or your CPU core count
next dev --turbopack

2. Use Webpack for now (stable fallback)

# Run without turbopack flag
next dev

3. Monitor and profile

# Check what's consuming CPU
top -p $(pgrep -f "next")

# Or use Node.js profiling
node --cpu-prof node_modules/.bin/next dev

4. File system watchers

If you have node_modules or large directories being watched:

// next.config.js
module.exports = {
  experimental: {
    turbopack: {
      // Exclude large directories from watching
      resolveAlias: {},
    }
  }
}

5. Report the issue

If the problem persists, file a bug at https://github.com/vercel/next.js/issues with:

• Your OS and CPU info
• next info output
• CPU profile file (from --cpu-prof)

This helps the Turbopack team optimize for real-world setups.

[PrashantSinghUP64]

I would be careful about installing a third-party package as the first fix here. High CPU from Turbopack is usually better debugged by isolating what Turbopack is watching/compiling.
A practical checklist:

1. Verify whether it is Turbopack-specific:
   bashnext dev --webpack
   If CPU drops with Webpack, you have a Turbopack repro worth reporting.
2. Clear local build/cache state:
   bashrm -rf .next
   npm run dev
3. Check for large watched folders accidentally inside the project:

generated files
logs
uploaded assets
large public/ folders
nested repos

4. If it still happens, generate a Turbopack trace:
   bashNEXT_TURBOPACK_TRACING=1 next dev
   Then share the trace along with your Next.js version, Node version, OS, and whether you're using App Router or Pages Router.
   The safe workaround is next dev --webpack for now — the useful long-term fix is a minimal reproduction or trace for the Next.js team