Standalone bootstrap and application configuration

Mental model

Bootstrap a standalone root component with bootstrapApplication and compose router, HTTP, hydration, error handling, and environment providers in ApplicationConfig. Keep the composition root small, use strict TypeScript, and prefer functional providers that remain tree-shakable.

Production practice

Design an app.config.ts that exposes no business logic and registers browser-safe platform services once. Make ownership, trusted boundaries, cancellation, accessibility, and failure states explicit before choosing an Angular abstraction.

Common failure modes

Watch for duplicated reactive sources, effects used as state propagation, unstable list keys, route guards mistaken for authorization, browser-only APIs during SSR, arbitrary async sleeps in tests, and optimizations made without measurements.

Takeaways

• Prefer explicit contracts and one owner for each state transition.
• Validate and authorize at the trusted server boundary.
• Test observable behavior, accessibility, and failure recovery.
• Measure bundles and user experience before optimizing.