2 ms·
Charitably, it could be nice for prototyping I'm going to assume you already know this shouldn't be done in production If you wanted something like this in pr
by brundolf 5y ago
Charitably, it could be nice for prototyping
I'm going to assume you already know this shouldn't be done in production
If you wanted something like this in production, then yes you could probably use modules and skip bundling these days, but skipping bundling != skipping transpiling. Instead, transpile your separate source modules into separate ES modules and ship those.
- tehbeard 5y agoWith HTTP/2 server push faltering in production and the real world... it's still best to bundle, but just down to your direct dependencies and with tree shaking (i.e. react and it's deps become one file, react-dom another, and any common deps between the two become a third "common-vendor.js" file). and while you're at it, it's not much more effort to take the ESM "evergreen" version, and dump a SystemJS IE11 / "legacy" bundle if needed for a project.