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.
You are exporting Main, just the one part, and the old Thing assembled back from new pieces. Library public API is not changed. This is no more than a minor bump.
You are exporting a Sidecar via another endpoint
....
You are assembling a Thing in a user space from Main and lazy Sidecar.
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.
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.
In your last example why do you load
library/sidecarlazily 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:
Thingfrom your librarythingtoMainandSidecarMain, just the one part, and the oldThingassembled back from new pieces. Library public API is not changed. This is no more than a minor bump.Sidecarvia another endpointThingin a user space fromMainand lazySidecar.Technically you may keep
importin 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.