Yeah... Its a tough one. With 5, I've been thinking of integrating with Bazel. They do some really nice package level dependency graph things, and incremental builds. So thinking a world there might be interesting to explore.
4 - I've been experimenting with another webpack plugin that is bespoke in the sense of finding all of the referenced containers, and spitting out a manifest shaped to how our url structure is. Could probably abstract it a little, and ship as a side-car plugin.
Thanks for joining us on this journey.
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.
Very nice! Considerations 4 & 5 have the potential to be painful. Looking forward to seeing how they are solved.
Keeping close watch on your progress here though - with an eye towards how to help support and work it into single-spa as well!
Yeah... Its a tough one. With 5, I've been thinking of integrating with Bazel. They do some really nice package level dependency graph things, and incremental builds. So thinking a world there might be interesting to explore.
4 - I've been experimenting with another webpack plugin that is bespoke in the sense of finding all of the referenced containers, and spitting out a manifest shaped to how our url structure is. Could probably abstract it a little, and ship as a side-car plugin.
Thanks for joining us on this journey.