Assuming you're only targeting > IE11 browsers, what's the hotness for serving users their JS? Particularly, static-served from a CDN like Cloudfront. Lots of iddybiddy modules served in parallel or a few chunkier things? I'm thinking @addyosmani or @slightlylate has a chart.
-
-
Replying to @gavindoughtie @addyosmani
As in, hosts? Servers? Generic patterns? Speaking super generally, the PRPL pattern is still the best I've ever seen on the wire for granularity & reuse. Required H/2 push. More approachably, ESM+Rollup+Workbox are great.
1 reply 0 retweets 3 likes -
Overall, there's a per-resource overhead that's not trivial (header parsing, lower compression ratios for smaller bodies, etc.), so some light bundling is usually good if you can get heavy code reuse (see devtools "coverage" panel for a cold-load) out of core bundles.
2 replies 0 retweets 1 like -
The thing I worry about is that ESM often leads to stair-step waterfalls where things are only requested when browser discovers the dep in module parsing. Tools like Rollup that can help you spot those per-route and generate <link as="script" rel="preload" ...> directives matter
2 replies 0 retweets 1 like
Seb Insua Retweeted lukejacksonn
Any thoughts on this POC? https://twitter.com/lukejacksonn/status/1260943184919658497?s=20 …https://twitter.com/lukejacksonn/status/1260943184919658497 …
Seb Insua added,
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.