rest of the JS community can't use turbopack, so they went with vite
Vite has been stable for years at least 5 years now and is built-upon because it's fast, stable, reliable and a bit less complicated than Webpack.
I always do that sort of thing in Docker so never considered it could be a Linux-specific thing, maybe so.
But the skepticism in this thread about ecosystem fragmentation is valid. Vite won because it worked with the existing ecosystem, not against it. Turbopack requiring Rust for plugins limits who can extend it.
That said, if you're already locked into Next.js, this is a clear win. The question is whether Next.js's market position justifies a separate build tool or whether this accelerates the trend of frameworks becoming walled gardens.
I personally love Vite and Remix.
The answer for people who need basically any build plugin is "use the webpack mode", and I have zero faith in Vercel maintaining that past the next major version.
I guess we'll see whether they figure out a story for plugins by then.
Webpack solved this problem with a few lines in the next.config.ts
For now, I’m back to using Webpack with NextJS 16 with the —Webpack flag. Hope they allow this for future versions.
There are plenty of complaints on the NextJS subreddit, and here is a open thread on complaints with Turbopack https://github.com/vercel/next.js/discussions/77721
Looks the alternative is Rspack?
``` turbopack: { resolveAlias: { fs: { browser: './empty-module.js' }, }, }, ```
so different configuration but similar to what you would do in webpack.
i am unsure about the other wasm issue you mentioned... is there an issue describing it?
As for webpack, we will keep supporting it until we know there are no compatibility issues blocking people from migrating.
> Many build systems include explicit dependency graphs that must be manually populated when evaluating build rules. Explicitly declaring your dependency graph can theoretically give optimal results, but in practice it leaves room for errors
Man this is the part I hate with turborepo
pjmlp•2w ago
The splitting communities effect always gets left out of these announcements, or gets positioned as something good.
lukesandberg•1w ago
I'm not sure i understand your second comment? what got positioned as 'something good'?