The micro-frontend SDK
for devedge
A small, public, mechanism-only SDK for Angular micro-frontends: a session seam the
shell owns, loud nav validation, and bearer wiring to a devedge-sdk backend.
The shell owns the session
One SessionProvider is instantiated once in the shell and threaded into every micro-frontend as a read-only view. Child micro-frontends read the token; they never authenticate.
Nav fails loud, not silent
A nav item’s group is validated against a host-supplied registry. An unknown group throws and names the bad value and the valid ones, instead of rendering nothing with no error.
Bearer wiring, once
createAuthedFetch and the Angular bearer interceptor attach the token and handle 401 with a single login-and-retry, so every micro-frontend calls the backend the same way.
A public seam, a private binding
Every seam here is a standard mechanism. Product-specific bindings — a provider’s OIDC authority, a nav taxonomy, a design system — live in separate private packages.
Thin lifecycle adapters
The single-spa and Angular adapters are thin glue over the same core contract. A shell composes them; the SDK carries no Angular CLI or ng-packagr.
A loud dev loop
devedge-ufe doctor turns the silent cert, CORS, manifest, and nav chain into an ordered checklist, so a broken local setup names its own failure.