The other 194 are in chunks that load when import is called within the code.
Some are quite deep in app logic and we really never want them for most visits. They are only called as necessary. We would maybe want to prefetch them once folks get close to where they would be hidden, but that's about it.
I guess it's all trade offs and from my point of view it seems like a good one.
Yeah, you still download it only one time
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I think this post by @quii is relevant to this discussion. I hope we can do a lot more to improve on this front.
The Web I Want
Chris James
This is cool, I haven't seen this technique before
Is there a chance it could make some features a bit slow when they're first used?
So if i click some button, it's now that it downloads, parses and executes the JS; which might be slow.
I guess it's all trade offs and from my point of view it seems like a good one.
Prefetching would be the next step but it requires more than 5 minutes:
The other 194 are in chunks that load when
import
is called within the code.Some are quite deep in app logic and we really never want them for most visits. They are only called as necessary. We would maybe want to prefetch them once folks get close to where they would be hidden, but that's about it.
Yeah, you still download it only one time