Application Not Mounting

Application Not Mounting Overview

Application Not Mounting lets you structure single-spa work so it stays readable, testable, and easy to scale. Instead of ad-hoc code, you follow a clear pattern that other developers can recognise immediately.

The key is to keep application not mounting focused and predictable. Start from the minimal example here, then layer in only the complexity your feature actually needs.

export async function bootstrap(props) {
  // one-time setup
}

export async function mount(props) {
  // render the app into props.domElement
}

export async function unmount(props) {
  // tear down and clean up
}

Every single-spa application exports bootstrap, mount, and unmount lifecycle functions.

Application Not Mounting Example

registerApplication({
  name: '@org/app',
  app: () => System.import('@org/app'),
  activeWhen: ['/app'],
});
start();

• Start from a minimal Application Not Mounting example and grow it only as needed.
• Keep configuration explicit so Application Not Mounting behaves the same in every environment.
• Name things clearly so teammates understand your Application Not Mounting at a glance.
• Add tests around Application Not Mounting early to lock in expected behaviour.

Single-SPA Cheatsheet

Core single-spa APIs related to application not mounting.

How Application Not Mounting Works in Single-SPA

Application Not Mounting is part of how single-spa lets multiple applications — even in different frameworks — coexist on one page. A root config registers each app and controls when it is active.

Every single-spa application exports bootstrap, mount, and unmount lifecycle functions.

• A root config registers apps and calls start().
• Each app exports bootstrap, mount, and unmount lifecycles.
• activeWhen decides which routes each app owns.
• Import maps resolve each app's bundle at runtime.

Practical Guidance for Application Not Mounting

For reliable micro frontends, application not mounting should isolate failures and keep shared state minimal. Let each team own its app end to end while agreeing on a few shared contracts.

Common Mistakes

• Skipping error handling and edge cases when wiring up application not mounting.
• Leaving application not mounting untested, so regressions slip into production.
• Over-engineering application not mounting before you actually need the extra flexibility.
• Ignoring documentation, which makes application not mounting hard for the next developer to change.

Key Takeaways

• Application Not Mounting is a core part of working effectively with single-spa.
• Start small and keep application not mounting focused on a single responsibility.
• Apply consistent patterns so application not mounting scales across your project.
• Test and document application not mounting to keep it maintainable over time.