4 ms·
Well, this might remove one argument against splitting the JS bundles too far. If you'll never benefit from eg. a shared JQuery library on a CDN anyway, might
by unilynx 7y ago
Well, this might remove one argument against splitting the JS bundles too far.
If you'll never benefit from eg. a shared JQuery library on a CDN anyway, might as well include a (reduced) version of it in your bundle.
- james-skemp 7y agoThat's as long as the shared library is changing about as frequently as your custom code. If you're using the same framework-x.y.z library for months at a time, but doing daily/weekly code changes and pushes, you're losing out on the cachability of the library. But if your project is only being updated as frequently as the third party libraries it uses, maybe it makes sense.