Angular and Zone.js

Angular and Zone.js Overview

Angular and Zone.js 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 angular and zone.js focused and predictable. Start from the minimal example here, then layer in only the complexity your feature actually needs.

import { singleSpaAngular } from 'single-spa-angular';
import { enableProdMode } from '@angular/core';
import { platformBrowserDynamic } from '@angular/platform-browser-dynamic';
import { AppModule } from './app/app.module';

export const { bootstrap, mount, unmount } = singleSpaAngular({
  bootstrapFunction: () => platformBrowserDynamic().bootstrapModule(AppModule),
  template: '<app-root />',
});

single-spa-angular wraps an Angular module as a single-spa micro frontend.

Angular and Zone.js Example

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

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

Single-SPA Cheatsheet

Core single-spa APIs related to angular and zone.js.

How Angular and Zone.js Works in Single-SPA

Angular and Zone.js 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.

single-spa-angular wraps an Angular module as a single-spa micro frontend.

• 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 Angular and Zone.js

For reliable micro frontends, angular and zone.js 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

• Copying angular and zone.js snippets without understanding what each line does.
• Skipping error handling and edge cases when wiring up angular and zone.js.
• Leaving angular and zone.js untested, so regressions slip into production.
• Over-engineering angular and zone.js before you actually need the extra flexibility.

Key Takeaways

• Angular and Zone.js is a core part of working effectively with single-spa.
• Start small and keep angular and zone.js focused on a single responsibility.
• Apply consistent patterns so angular and zone.js scales across your project.
• Test and document angular and zone.js to keep it maintainable over time.