A microfrontend setup needs a way to compose applications, load shared code, and test changes across application boundaries. These packages address different parts of that work. Start by deciding whether you need Angular build integration, support for an existing Next.js integration, application lifecycle orchestration, or a way to test a local module in an existing environment.
Module Federation addresses sharing code across builds. The Angular plugin integrates that mechanism into an Angular project. The Next.js plugin is relevant when maintaining an existing Pages Router integration, with its documented router constraint.
single-spa coordinates when applications become active and how they mount and unmount. Import maps decide which URL supplies a module. For a shell that already uses an import map, import-map-overrides can redirect a module to a local development server while the rest of the shell uses its configured modules. The override is useful for development and debugging. Deploy application changes through the project’s normal release process.
Use single-spa when a shell must mount and unmount independently implemented applications as navigation changes. Pick a module-loading and deployment strategy alongside it.
Use the Angular Architects plugin when Angular applications need to expose or consume modules through Module Federation. Check the host and remote build configurations together, particularly which dependencies they share.
Treat this as a maintenance consideration for an existing Next.js Pages Router project that already uses the plugin. The project documents its deprecation and does not support App Router, so an App Router migration requires a different integration strategy.
Use this when the shell already resolves modules through an import map and you want to test one local module alongside deployed ones. Keep the environment’s base import map in place so other modules still resolve as configured.
Build micro frontends that coexist and can (but don't need to) be written with their own framework. This allows you to:
To add your company's logo to this section:
You can find the single-spa documentation on the website.
Check out the Getting Started page for a quick overview.
Please see the examples page on the website.
Want to file a bug, contribute some code, or improve documentation? Excellent! Read up on our guidelines for contributing on the single-spa website.
The main purpose of this repository is to continue to evolve single-spa, making it better and easier to use. Development of single-spa, and the single-spa ecosystem happens in the open on GitHub, and we are grateful to the community for contributing bugfixes and improvements. Read below to learn how you can take part in improving single-spa.
Single-spa has adopted a Code of Conduct that we expect project participants to adhere to. Please read the full text so that you can understand what actions will and will not be tolerated.
Read our contributing guide to learn about our development process, how to propose bugfixes and improvements, and how to build and test your changes to single-spa.