131–140 of 331 posts
Earlier quoted context omitted.
JS has 10x the amount of developers of all other languages combined, that translates to a lot of ideas on how to progress the different avenues of JS land.
It is also the primary language taught to bootcamp developers looking to get started, and so a lot of suggestions and ideas come from people without any real experience.
The Turbo memoization framework sounds interesting, but I don't see any code samples for what it looks like for Rust users, or how it compares to other Rust memoization/caching libraries…
In several places it is mentioned as a Rust library, but I don't see any links to it. Using google search I'm not finding a Rust library named "Turbo". Is the library open source, or available on crates.io / in a public repo somewhere?
And the github link at the top of the page links here: https://github.com/vercel/turbo but, despite being called "turbo", that seems to actually be the repo for Turbopack (the webpack alternative) not "Turbo" the library.
Even digging a bit into the crates, I'm not sure where this supposed library lives: https://github.com/vercel/turbo/tree/main/crates
A bit of a bummer that "get started" requires nextjs, and there's no documentation for a frameworkless build (I understand it's labeled as alpha but if you're going for such grandiose announcement an "how to bundle a vanilla/frameworkless app" would have been nice)
Surprised not to see much mention of plugins and how they will work (unless I missed something?). Plugins are the big differentiator between Webpack and existing "webpack but faster" tools, and presumably the reason most people still use webpack. What's the plan here?
"In future versions, we'll be supporting Vue and Svelte via plugins."
https://turbo.build/pack/docs/features/frameworks#vue-and-sv...
Earlier quoted context omitted.
Currently looking at a 1000 line webpack config..........
You're either doing something complicated or you're not using Webpack very well. Most Webpack config I've worked with isn't like that.
Really hope this gets a competent library mode. Webpacks library mode never really evolved to meet the needs of things. Vite has a good library mode but it has its own limitations. Pure rollup is still the best for building libraries, by and large (maybe esbuild now? but I think rollup is more efficient in its output still). If this has a good, solid library mode that works like rollup with the power of the webpack-l…
Yes. I mostly build libraries and rollup still beats everything in compatibility (esm, umd, cjs, etc) and output quality. It's slow, though, and I would love a faster alternative. Esbuild doesn't do tree shaking as well as rollup.
I noted that esbuild doesn't fully support es5 transpilation and this will hold it back from some usage.
Is there any actual proof that Turbopack is 10x faster than Vite at anything? I can't find any benchmark showing it.
I'm a little skeptical as well. Vite is fast I just checked a code base that's at ~900 modules, and vite is ready to serve dev requests in well under a second.
Surprised not to see much mention of plugins and how they will work (unless I missed something?). Plugins are the big differentiator between Webpack and existing "webpack but faster" tools, and presumably the reason most people still use webpack. What's the plan here?
It sounds like plugins will be a thing but existing webpack plugins will need to be ported.