@angular/upgrade/static

UpgradeModule

NgModule

An NgModule, which you import to provide AngularJS core services, and has an instance method used to bootstrap the hybrid upgrade application.

  
    class UpgradeModule {}

An NgModule, which you import to provide AngularJS core services, and has an instance method used to bootstrap the hybrid upgrade application.

Part of the upgrade/static library for hybrid upgrade apps that support AOT compilation

The upgrade/static package contains helpers that allow AngularJS and Angular components to be used together inside a hybrid upgrade application, which supports AOT compilation.

Specifically, the classes and functions in the upgrade/static module allow the following:

Creation of an Angular directive that wraps and exposes an AngularJS component so that it can be used in an Angular template. See UpgradeComponent.
Creation of an AngularJS directive that wraps and exposes an Angular component so that it can be used in an AngularJS template. See downgradeComponent.
Creation of an Angular root injector provider that wraps and exposes an AngularJS service so that it can be injected into an Angular context. See Upgrading an AngularJS service below.
Creation of an AngularJS service that wraps and exposes an Angular injectable so that it can be injected into an AngularJS context. See downgradeInjectable.
Bootstrapping of a hybrid Angular application which contains both of the frameworks coexisting in a single application.

          import {UpgradeModule} from '@angular/upgrade/static';

See also the {@link UpgradeModule#examples examples} below.

Mental Model

When reasoning about how a hybrid application works it is useful to have a mental model which describes what is happening and explains what is happening at the lowest level.

There are two independent frameworks running in a single application, each framework treats the other as a black box.
Each DOM element on the page is owned exactly by one framework. Whichever framework instantiated the element is the owner. Each framework only updates/interacts with its own DOM elements and ignores others.
AngularJS directives always execute inside the AngularJS framework codebase regardless of where they are instantiated.
Angular components always execute inside the Angular framework codebase regardless of where they are instantiated.
An AngularJS component can be "upgraded"" to an Angular component. This is achieved by defining an Angular directive, which bootstraps the AngularJS component at its location in the DOM. See UpgradeComponent.
An Angular component can be "downgraded" to an AngularJS component. This is achieved by defining an AngularJS directive, which bootstraps the Angular component at its location in the DOM. See downgradeComponent.
Whenever an "upgraded"/"downgraded" component is instantiated the host element is owned by the framework doing the instantiation. The other framework then instantiates and owns the view for that component.
1. This implies that the component bindings will always follow the semantics of the instantiation framework.
2. The DOM attributes are parsed by the framework that owns the current template. So attributes in AngularJS templates must use kebab-case, while AngularJS templates must use camelCase.
3. However the template binding syntax will always use the Angular style, e.g. square brackets ([...]) for property binding.
Angular is bootstrapped first; AngularJS is bootstrapped second. AngularJS always owns the root component of the application.
The new application is running in an Angular zone, and therefore it no longer needs calls to $apply().

The `UpgradeModule` class

This class is an NgModule, which you import to provide AngularJS core services, and has an instance method used to bootstrap the hybrid upgrade application.

Core AngularJS services
Importing this NgModule will add providers for the core AngularJS services to the root injector.
Bootstrap
The runtime instance of this class contains a {@link UpgradeModule#bootstrap bootstrap()} method, which you use to bootstrap the top level AngularJS module onto an element in the DOM for the hybrid upgrade app.

It also contains properties to access the {@link UpgradeModule#injector root injector}, the bootstrap NgZone and the AngularJS $injector.

Examples

Import the UpgradeModule into your top level {@link NgModule Angular NgModule}.

Then inject UpgradeModule into your Angular NgModule and use it to bootstrap the top level AngularJS module in the ngDoBootstrap() method.

Finally, kick off the whole process, by bootstrapping your top level Angular NgModule.

{@a upgrading-an-angular-1-service}

Upgrading an AngularJS service

There is no specific API for upgrading an AngularJS service. Instead you should just follow the following recipe:

Let's say you have an AngularJS service:

Then you should define an Angular provider to be included in your NgModule providers property.

Then you can use the "upgraded" AngularJS service by injecting it into an Angular component or service.

$injector

any

The AngularJS $injector for the upgrade application.

injector

Injector

The Angular Injector *

ngZone

NgZone

The bootstrap zone for the upgrade application

bootstrap

any

Bootstrap an AngularJS application from this NgModule

@paramelementElement

the element on which to bootstrap the AngularJS application

@parammodulesstring[]

the AngularJS modules to bootstrap for this application

@paramconfigany

optional extra AngularJS bootstrap configuration

@returnsany