Code splitting. Code splitting is everywhere. However, why? Just because there is too much of javascript nowadays, and not all are in use at the sa...
For further actions, you may consider blocking this person and/or reporting abuse
In your last example why do you load
library/sidecar
lazily but in your library use it as a static import?Not really fully on that boat yet, great article by the way. Love reading your articles since every concept has a well-defined example attached to it.
It was more about:
Thing
from your librarything
toMain
andSidecar
Main
, just the one part, and the oldThing
assembled back from new pieces. Library public API is not changed. This is no more than a minor bump.Sidecar
via another endpointThing
in a user space fromMain
and lazySidecar
.Technically you may keep
import
in a library code, but you will loose control on chunk name and prefetching.As I said - this is a subject to complete and argue about.
Amazing read! 👏 Thanks Anton! 💯