2 ms·
Very excited for this if the configuration and behavior is 1:1 with Webpack. The primary reason I haven't moved to other "more efficient" build tools is having
by jdelman 4y ago
Very excited for this if the configuration and behavior is 1:1 with Webpack. The primary reason I haven't moved to other "more efficient" build tools is having to learn how to do various optimizations and getting the artifacts I expect.
- TheRealPomax 4y agoGod, I hope not. If there's one part of webpack that needs a complete overhaul it's (1) how you set up complex workflow configurations and (2) proper documentation for all aspects of that. And yes, that's one thing. Code without docs is not production-ready code, but code with bad docs isn't even PoC-ready code.
- crucialfelix 4y agoI think webpack has overhauled 1 and 2 every major release. Accordingly the docs and API and blogs are littered with a mish mash of all previous APIs. Thats the whole problem with webpack-its always changing.
- fabian2k 4y ago> Webpack has a huge API. It's extremely flexible and extensible, which is a big reason why it's so popular. > We're planning on making Turbopack very flexible and extensible, but we're not planning 1:1 compatibility with Webpack. This lets us make choices which improve on Webpack's API, and let us optimize for speed and efficiency. https://turbo.build/pack/docs/migrating-from-webpack https://turbo.build/pack/docs/migrating-from-webpack