11–20 of 26 posts
Earlier quoted context omitted.
turbopack is tightly coupled with next.js rest of the JS community can't use turbopack, so they went with vite
[dead]
But that is not representative of broader ecosystem.
This thing can't be replaced by bun on Linux.
Is this a quip I’m not understanding or is there really something here that bun‘s bundled wouldn’t be able to do? Because I can’t find anything.
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?
I may be out of the loop, but isn't the JS/TS community consolidating around Vite? https://vite.dev/
The fact that there's no tangible plan for any plugin support in Turbopack is actually what made me not choose Next.js. 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.
> 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
I may be out of the loop, but isn't the JS/TS community consolidating around Vite? https://vite.dev/
turbopack is tightly coupled with next.js 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.