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
Create a new Next.js project (v15)
Run npm init builder.io@latest
Follow CLI prompts
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.
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.