How pankajpat85/angular-spa works
Project type and purpose
• This is a micro-frontend system built with Angular and orchestrated by Single-SPA.
• There are four main Angular apps:
• root (the single-spa “root-config”/shell)
• layout (a layout/navigation micro-frontend)
• profile (a user-profile micro-frontend)
• settings (a settings micro-frontend)
• The LinkedIn article explains how Single-SPA loads each Angular app as a separate bundle at runtime.
File structure
• Top level:
• README.md – points to the implementation article
• layout/, profile/, settings/ – each is an Angular project with its own package.json, angular.json, src/app, single-spa-webpack.config.js, tsconfigs
• root/ – contains the Single-SPA root-config and HTML template (microfrontend-layout.html), webpack.config.js, angular19-root-config.ts
• Each micro-frontend follows the same pattern:
• src/app/app.routes.ts – declares Single-SPA routes (mount points)
• src/app/app.config.ts – Single-SPA lifecycles (bootstrap, mount, unmount)
• EmptyRoute folder – a placeholder component to handle non-matched routes.
• Configuration files: single-spa-webpack.config.js in each micro-frontend, root’s webpack.config.js for the shell.
README for additional insights
• The README simply points to an article describing an Angular-based micro-frontend architecture using Single-SPA.
Elements
• Browser → Root (initial load)
• Root → micro-frontends (fetch/registration)
• Browser navigation → Single-SPA → mount/unmount lifecycles
• Shell (blue), micro-frontends (green), shared deps (yellow), client (gray).