2 ms·
I think the ultimate solution to bundling is to go the way of the CLIs, and Angular CLI in particular, where the framework team configures a sensible default bu
by jf- 8y ago
I think the ultimate solution to bundling is to go the way of the CLIs, and Angular CLI in particular, where the framework team configures a sensible default bundle config with a few options exposed via the CLI. The user can then build with a single command and everything just works. The user can eject from the CLI and configure manually if needs be, but most of the time that won’t be necessary.
Bundlers probably have a certain minimum complexity that can’t be reduced if they want to be universally applicable, but a lot of that can be hidden for most use cases, particularly if using the same framework.
- awesomepeter 8y agoYup, just FYI Angulars CLI is based on Embers. Just putting it out there because the oldest thriving framework which put out a lot of great ideas often gets forgotten in these discussions :)
- jf- 8y agoWas not aware, thanks for mentioning it!
- Fifer82 8y agoWhat is WebPack and SystemJS? I am being tongue in cheek but I totally agree. See all this bundling stuff? Nothing is more boring and lifeless to me personally and Angular CLI has shielded me from all of it. Really great project. The only real problem I am having is lazy loading and dynamic component's. I am being forced really to add routes to lazy load some heavy components but I would really like not to have to deal with that. I believe there is a way to use SystemJS to load dynamic components at runtime but there is scant information and have no interest to pursue it. A small price to pay.