3 ms·
Startup speed is terrible with that approach, each browserified module adds like 10x more code as boilerplate than something like isArray implementation would t
by esailija 10y ago
Startup speed is terrible with that approach, each browserified module adds like 10x more code as boilerplate than something like isArray implementation would take. Then every module dependency is resolved dynamically at runtime, which will also quickly become a performance problem even when you aren't using micromodules.
- Klathmon 10y agoI haven't touched browserify, but with webpack what you said could not be more false... Webpack doesn't bundle at runtime, it doesn't add any amount of code overhead per module that I can easily measure, and it doesn't trash startup speed.
- nilliams 10y agoSame goes for browserify. You can have lots of tiny modules and (watchify especially) is fast to re-build. And yeah perf of 'require' statements at run-time is a non-issue.
- 15155 10y ago> it doesn't add any amount of code overhead per module It's something like tens of bytes (minified), FWIW, for the closure that each module gets put into.