Hi @Polar bear, turbopack is used only for bundling it doesn't work on server. Turbopack is stable so you can use it. I think they mean that turbo configuration is experimental and can change as it's mark as experimental.

The turbo configuration afaik does not actually enable turbo it just configures it, to enable it you need to modify the next dev script to be next dev --turbopack this is supported, but if you tried to do next build --turbopack your build will likely fail, and if it doesn't then you will run into countless issues.

The docs are not clear and the two links above make it hard to make a sense.
Would like a clarification from someone who’s certain

alone turbopack is stable https://nextjs.org/blog/turbopack-for-development-stable

so only turbo config is experimental

I know but putting turbo config makes things unstable? In prod?

Even if there’s no config options inside

if you change default behaviour of turbopack (config) it can brake, because of that it is marked as experimental

yeah, I know that, too. Guess I won’t get a definitive answer, but nvm.

Just hope that someone from Vercel sees that and clarifies or just fixes the docs to be more clear.