September 2026

Every kindergarten class has two kids.

One hoards the blocks and won't let anyone near them.

The other gives away all his toys and goes home with nothing.

Monorepos have both, and neither of them is having a good time.

Sharing code is why we build monorepos in the first place, but shared code without boundaries turns into a shared folder that owns everything and can't be changed by anyone.

In this talk we'll walk through an Nx workspace structure that makes boundaries obvious before you enforce them, then set up those boundaries properly with tags and dependency constraints.

From there, we'll look at the sharing decisions that actually come up day to day, and at what separates code that's genuinely shared from code that just ended up in the same folder.

Module Federation is a runtime model for loading and sharing modules between independently deployed builds.

In Angular, it can be implemented through different toolchains depending on the underlying build system.

Angular’s default setup uses its own CLI-based build pipeline, but it also explicitly supports custom build pipelines.

This enables alternative implementations such as Rspack and Vite-based setups.

These approaches move away from the standard Angular toolchain and introduce additional responsibility around build integration, compatibility, and long-term maintenance.

In this talk, we explore the implications of adopting custom build pipelines for Module Federation in Angular, and what changes when moving beyond the default tooling.