Angular

Angular is a TypeScript-oriented web application framework maintained by Google. It provides a structured approach to building browser applications, including component-based UI composition, dependency injection, routing, forms, HTTP tooling, testing support, and build tooling. It is commonly used for large applications where conventions, strong typing, and an integrated framework architecture are valuable. Angular is not AngularJS: AngularJS is a separate, earlier framework with its own versions and its own end of life. Anyone running AngularJS should see /technology/angularjs instead.

Angular emerged as a redesign of the earlier AngularJS approach, replacing its scope-and-controller model with a component-based architecture and a stronger emphasis on TypeScript, dependency injection, templates, and ahead-of-time compilation. Its ecosystem initially centered on framework-managed modules and a command-line workspace tool. Later releases increasingly emphasized simpler standalone application composition, improved rendering and reactivity primitives, faster builds, server-side rendering and hydration, and a more streamlined developer experience. Although applications built in different Angular eras can often coexist with modern tooling, the recommended architectural patterns have changed substantially over time.

Migration to Angular commonly involves adopting its opinionated application structure, TypeScript conventions, template syntax, dependency-injection model, router, and build pipeline. Teams moving from less structured libraries may need to reorganize state management, data access, forms, and component boundaries rather than merely translating UI code. Server rendering can add further work around browser-only APIs, request-specific state, hydration behavior, and deployment configuration. Migration between older and newer Angular application styles can require replacing module-centric patterns, revisiting initialization and provider configuration, and updating third-party libraries that depend on older APIs or build assumptions. Moving away from Angular may require extracting business logic from framework services, replacing template and form behavior, recreating routing and dependency-injection patterns, and choosing alternatives for testing, internationalization, rendering, and builds. The largest cost is usually application-specific coupling to Angular templates, reactive patterns, framework services, and ecosystem packages rather than the component markup alone.