Turbopack incompatibility with Builder.io's devtools CLI

Builder content link
N/A - This is an initialization issue

Builder public api key
N/A - Unable to get to this stage due to initialization failure

Detailed steps to reproduce the bug

  1. Create a new Next.js project (v15)
  2. Run npm init builder.io@latest
  3. Follow CLI prompts
  4. Receive error: “Turbopack does not support the Builder.io devtools cli. Please disable Turbopack or manually integrate Builder.io into your Next.js project.

Code stack you are integrating Builder with

  • Next.js
  • Turbopack
  • Node.js

Reproducible code example
This is a CLI initialization error, occurs with default Next.js setup when using Turbopack.

Hello @MR2025,

Thanks for bringing this to our attention. We’re aware of the issue and wanted to share some context.

It appears that Turbopack currently doesn’t support webpack plugins, which is how Builder dev tools integrate with webpack. You can find more details about this in the Turbopack migration docs. Additionally, Turbopack doesn’t yet support production builds, as noted in the getting started guide.

Given these limitations, we’ve decided not to make Turbopack compatible at this time, but instead, we’re showing a warning to inform users.

Let us know if you have any further questions!

Thanks,

Hi Manish,

Thanks for the update!

Would disabling Turbopack and reverting to Webpack be the most straightforward solution, or are there alternative approaches you’d recommend?

Best

Hello @MR2025,

Yes, disabling Turbopack and reverting to Webpack would be the most straightforward solution. There are no alternative approaches at the moment.

Thanks,

Download Turbopack Incompatibility Crack


.

.
.
.
.

.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.