Architecture overview

Angular is a platform and framework for building client applications in HTML and TypeScript.

Angular is itself written in TypeScript.

It implements core and optional functionality as a set of TypeScript libraries that you import into your apps.

The basic building blocks of an Angular application are NgModules,

which provide a compilation context for components.

NgModules collect related code into functional sets;

an Angular app is defined by a set of NgModules.

An app always has at least a root module that enables bootstrapping,

and typically has many more feature modules.

Components define views, which are sets of screen elements that Angular can choose among and modify according to your program logic and data. Every app has at least a root component.
Components use services, which provide specific functionality not directly related to views. Service providers can be injected into components as dependencies, making your code modular, reusable, and efficient.

Both components and services are simply classes,

with decorators that mark their type

and provide metadata that tells Angular how to use them.

The metadata for a component class associates it with a template that defines a view.
A template combines ordinary HTML with Angular directives
and binding markup that allow Angular to modify the HTML before rendering it for display.
The metadata for a service class provides the information Angular needs to make it available to components through Dependency Injection (DI).

An app's components typically define many views, arranged hierarchically.

Angular provides the Router service to help you define navigation paths among views.

The router provides sophisticated in-browser navigational capabilities.

Modules

Angular defines the NgModule,

which differs from and complements the JavaScript (ES2015) module.

An NgModule declares a compilation context for a set of components

that is dedicated to an application domain, a workflow, or a closely related set of capabilities.

An NgModule can associate its components with related code, such as services, to form functional units.

Every Angular app has a root module, conventionally named AppModule,

which provides the bootstrap mechanism that launches the application.

An app typically contains many functional modules.

Like JavaScript modules,

NgModules can import functionality from other NgModules,

and allow their own functionality to be exported

and used by other NgModules.

For example, to use the router service in your app, you import the Router NgModule.

Organizing your code into distinct functional modules

helps in managing development of complex applications,

and in designing for reusability.

In addition, this technique lets you take advantage of lazy-loading

—that is, loading modules on demand—

in order to minimize the amount of code that needs to be loaded at startup.

For a more detailed discussion, see Introduction to modules.

Components

Every Angular application has at least one component,

the root component that connects a component hierarchy with the page DOM.

Each component defines a class that contains application data and logic,

and is associated with an HTML template that defines a view to be displayed in a target environment.

The @Component decorator identifies the class immediately below it as a component,

and provides the template and related component-specific metadata.

Decorators are functions that modify JavaScript classes.

Angular defines a number of such decorators that attach specific kinds of metadata to classes,

so that it knows what those classes mean and how they should work.

Learn more about decorators on the web.

Templates, directives, and data binding

A template combines HTML with Angular markup

that can modify the HTML elements before they are displayed.

Template directives provide program logic, and binding markup connects your application data and the document object model (DOM).

Event binding lets your app respond to user input in the target environment by updating your application data.
Property binding lets you interpolate values that are computed from your application data into the HTML.

Before a view is displayed,

Angular evaluates the directives and resolves the binding syntax

in the template to modify the HTML elements and the DOM,

according to your program data and logic.

Angular supports two-way data binding,

meaning that changes in the DOM,

such as user choices, can also be reflected back into your program data.

Your templates can also use pipes to improve the user experience by transforming values for display.

Use pipes to display,

for example,

记笔记,划重点 dates and currency values in a way appropriate to the user's locale.

Angular provides predefined pipes for common transformations, and you can also define your own.

举个最简单的栗子:

Angular2日期格式化

一、ts中调用

1.引入： import { DatePipe } from '@angular/common';

2.加入构造函数：

constructor(

private http: Http,

private alertService: AlertService,

private datePipe: DatePipe,

) { }

3.方法中调用

let dateStr:string = this.datePipe.transform(data.detailList[i].checkDate,'yyyy-MM-dd');

二、html中日期格式化

　　<div class="content"> {{chkCheck.checkDate | date: 'yyyy-MM-dd'}}</div>

</div>

For a more detailed discussion of these concepts, see Introduction to components.

Services and dependency injection ( 简称 DI )

For data or logic that is not associated with a specific view,

and that you want to share across components,

you create a service class.

A service class definition is immediately preceded by the @Injectable decorator.

The decorator provides the metadata

that allows your service to be injected into client components as a dependency.

Dependency injection (or DI) lets you keep your component classes lean and efficient.

They (就是Components) don't fetch data from the server, validate user input, or log directly to the console;

they (就是Components) delegate such tasks to services.

For a more detailed discusssion, see Introduction to services and DI.

Routing

The Angular Router NgModule provides a service

that lets you define a navigation path

among the different application states and view hierarchies in your app.

It is modeled on the familiar browser navigation conventions (人们熟知的浏览器导航习惯):

Enter a URL in the address bar and the browser navigates to a corresponding page.
Click links on the page and the browser navigates to a new page.
Click the browser's back and forward buttons and the browser navigates backward and forward through the history of pages you've seen.

The router maps URL-like paths to views instead of pages.

When a user performs an action, such as clicking a link, that would load a new page in the browser,

the router intercepts (拦截) the browser's behavior, and shows or hides view hierarchies.

If the router determines that the current application state requires particular functionality,

and the module that defines it has not been loaded, the router can lazy-load the module on demand.

The router interprets a link URL according to your app's view navigation rules and data state.

You can navigate to new views when the user clicks a button, selects from a drop box,

or in response to some other stimulus from any source.

The Router logs activity in the browser's history journal,

so the back and forward buttons work as well.

To define navigation rules, you associate navigation paths with your components.

A path uses a URL-like syntax that integrates your program data,

in much the same way that template syntax integrates your views with your program data.

You can then apply program logic to choose which views to show or to hide,

in response to user input and your own access rules.

For a more detailed discussion, see Routing and navigation.

What's next

You've learned the basics about the main building blocks of an Angular application.

The following diagram shows how these basic pieces are related.

Together, a component and template define an Angular view.
- A decorator on a component class adds the metadata, including a pointer to the associated template.
- Directives and binding markup in a component's template modify views based on program data and logic.
The dependency injector provides services to a component, such as the router service that lets you define navigation among views.

Each of these subjects is introduced in more detail in the following pages.

Modules
Components
- Templates
- Metadata
- Data binding
- Directives
- Pipes
Services and dependency injection

Note that the code referenced on these pages is available as a live example / download example.

When you are familiar with these fundamental building blocks,

you can explore them in more detail in the documentation.

To learn about more tools and techniques that are available to help you build and deploy Angular applications, see Next steps.

Introduction to modules

Angular apps are modular and Angular has its own modularity system called NgModules.

An NgModule is a container for a cohesive block of code

dedicated to an application domain, a workflow, or a closely related set of capabilities.

It can contain components, service providers, and other code files

whose scope is defined by the containing NgModule.

It can import functionality that is exported from other NgModules,

and export selected functionality for use by other NgModules.

意思是: 模块可以导入被其他模块导出的 functionality

模块也可以导出特定的functionality供其他模块使用

Every Angular app has at least one NgModule class, the root module,

which is conventionally named AppModule

and resides in a file named app.module.ts.

You launch your app by bootstrapping the root NgModule.

While a small application might have only one NgModule,

但是 most apps have many more feature modules.

The root NgModule for an app is so named

because it can include child NgModules in a hierarchy of any depth.

NgModule metadata

An NgModule is defined as a class decorated with @NgModule.

The @NgModule decorator is a function

that takes a single metadata object (只有一个对象作为函数参数),

whose properties describe the module.

The most important properties are as follows.

declarations — The components, directives, and pipes that belong to this NgModule.
exports —The subset (子集) of declarations that should be visible and usable in the component templates of other NgModules.
imports — Other modules whose exported classes are needed by component templates declared in this NgModule.
providers—Creators of services that this NgModule contributes to the global collection of services;
they become accessible in all parts of the app.
(You can also specify providers at the component level, which is often preferred.)
bootstrap — The main application view, called the root component, which hosts all other app views.
Only the root NgModule should set this bootstrap property.

Here's a simple root NgModule definition:

src/app/app.module.ts

content_copyimport { NgModule }      from '@angular/core';
import { BrowserModule } from '@angular/platform-browser';
@NgModule({
  imports:      [ BrowserModule ],
  providers:    [ Logger ],
  declarations: [ AppComponent ],
  exports:      [ AppComponent ],
  bootstrap:    [ AppComponent ]
})
export class AppModule { }

The export of AppComponent is just to show how to export;

it isn't actually necessary in this example.

A root NgModule has no reason to export anything

because other modules don't need to import the root NgModule.

NgModules and components

NgModules provide a compilation context for their components.

A root NgModule always has a root component that is created during bootstrap,

but any NgModule can include any number of additional components,

which can be loaded through the router or created through the template.

The components that belong to an NgModule share a compilation context.

A component组件 and its template模板 together define a view.

A component can contain a view hierarchy,

which allows you to define arbitrarily complex areas of the screen

that can be created, modified, and destroyed as a unit.

A view hierarchy can mix views defined in components that belong to different NgModules.

This is often the case, especially for UI libraries.

When you create a component,

it is associated directly with a single view, called the host view.

The host view can be the root of a view hierarchy,

which can contain embedded views (which are in turn the host views of other components).

意思就是: 这个 host view 是视图层次结构的根,

这个host view 包含了其他的view

而其他的view 同样的又是其他 component的 host view (即根)

Those components can be in the same NgModule, or can be imported from other NgModules.

Views in the tree can be nested to any depth.

The hierarchical structure of views is a key factor in the way

Angular detects and responds to changes in the DOM and app data.

NgModules and JavaScript modules

The NgModule system is different from and unrelated to the JavaScript (ES2015) module system

for managing collections of JavaScript objects.

These are two different and complementary module systems.

You can use them both to write your apps.

In JavaScript each file is a module

and all objects defined in the file belong to that module.

The module declares some objects to be public by marking them with the export key word.

Other JavaScript modules use import statements to access public objects from other modules.

import { NgModule }     from '@angular/core';
import { AppComponent } from './app.component';

export class AppModule { }

Learn more about the JavaScript module system on the web.

Angular libraries

Angular ships as a collection of JavaScript modules.

ship这个词用得妙啊, 意思就是: ???

You can think of them as library modules.

Each Angular library name begins with the @angular prefix.

Install them with the npm package manager

and import parts of them with JavaScript import statements.

For example, import Angular's Component decorator from the @angular/core library like this:

import { Component } from '@angular/core';

You also import NgModules from Angular libraries using JavaScript import statements:

import { BrowserModule } from '@angular/platform-browser';

In the example of the simple root module above,

the application module needs material from within the BrowserModule

To access that material,

add it to the @NgModule metadata imports like this.

imports: [BrowserModule],

In this way you're using both the Angular and JavaScript module systems together.

Although it's easy to confuse the two systems,

which share the common vocabulary of "imports" and "exports",

you will become familiar with the different contexts in which they are used.

Learn more from the NgModules page.

Introduction to components

A component controls a patch ( 小块 ) of screen called a view.

For example, individual components define and control each of the following views from the Tutorial:

The app root with the navigation links.
The list of heroes.
The hero editor.

You define a component's application logic

—what it does to support the view—

inside a class.

The class interacts with the view through an API of properties and methods.

For example, the HeroListComponent has a heroes property

that returns an array of heroes

that it acquires from a service.

HeroListComponent also has a selectHero() method

that sets a selectedHero property

when the user clicks to choose a hero from that list.

src/app/hero-list.component.ts (class)

export class HeroListComponent implements OnInit {
  heroes: Hero[];
  selectedHero: Hero;

  constructor(private service: HeroService) { }

  ngOnInit() {
    this.heroes = this.service.getHeroes();
  }

  selectHero(hero: Hero) { this.selectedHero = hero; }
}

Angular creates, updates, and destroys components

as the user moves through the application.

Your app can take action at each moment in this lifecycle

through optional lifecycle hooks, like ngOnInit().

Component metadata

The @Component decorator identifies the class immediately below it

as a component class, and specifies its metadata.

In the example code below,

you can see that HeroListComponent is just a class,

with no special Angular notation or syntax at all.

It's not a component until you mark it as one with the @Component decorator.

The metadata for a component

tells Angular where to get the major building blocks it needs

to create and present the component and its view.

In particular, it associates a template with the component,

either directly with inline code, or by reference.

Together, the component and its template describe a view.

In addition to containing or pointing to the template,

the @Component metadata configures,

for example, how the component can be referenced in HTML (用啥样的自定义标签)

and what services it requires.

Here's an example of basic metadata for HeroListComponent:

src/app/hero-list.component.ts (metadata)

@Component({
  selector:    'app-hero-list',
  templateUrl: './hero-list.component.html',
  providers:  [ HeroService ]
})
export class HeroListComponent implements OnInit {
/* . . . */
}

This example shows some of the most useful @Component configuration options:

selector: A CSS selector that tells Angular to create and insert an instance of this component
wherever it finds the corresponding tag in template HTML.
For example, if an app's HTML contains <app-hero-list></app-hero-list>,
then Angular inserts an instance of the HeroListComponent view between those tags.
templateUrl: The module-relative address of this component's HTML template.
Alternatively, you can provide the HTML template inline,
as the value of the template property. This template defines the component's host view.
providers: An array of dependency injection providers for services that the component requires.
In the example, this tells Angular that the component's constructor requires a HeroService instance
in order to get the list of heroes to display.

Templates and views

You define a component's view with its companion template.

A template is a form of HTML

that tells Angular how to render the component.

Views are typically arranged hierarchically,

allowing you to modify or show and hide entire UI sections or pages as a unit.

The template immediately associated with a component defines that component's host view.

这句话等价于:

The template associated with a component immediately defines that component's host view.

The component can also define a view hierarchy,

which contains embedded views, hosted by other components.

A view hierarchy can include views from components in the same NgModule,

but it also can (and often does) include views from components that are defined in different NgModules.

Template syntax

A template looks like regular HTML,

except that it also contains Angular template syntax,

which alters the HTML based on your app's logic and the state of app and DOM data.

Your template can use data binding to coordinate the app and DOM data,

pipes to transform data before it is displayed,

and directives to apply app logic to what gets displayed.

For example, here is a template for the Tutorial's HeroListComponent:

src/app/hero-list.component.html

<h2>Hero List</h2>

<p><i>Pick a hero from the list</i></p>
<ul>
  <li *ngFor="let hero of heroes" (click)="selectHero(hero)">
    {{hero.name}}
  </li>
</ul>

<app-hero-detail *ngIf="selectedHero" [hero]="selectedHero"></app-hero-detail>

This template uses typical HTML elements like <h2> and <p>,

and also includes Angular template-syntax elements,

*ngFor, {{hero.name}}, (click), [hero], and <app-hero-detail>.

The template-syntax elements tell Angular how to render the HTML to the screen, using program logic and data.

The *ngFor directive tells Angular to iterate over a list.
The {{hero.name}}, (click), and [hero] bind program data to and from the DOM,
responding to user input. See more about data binding below.
The <app-hero-detail> tag in the example is an element
that represents a new component, HeroDetailComponent.
The HeroDetailComponent (code not shown) is a child component of the HeroListComponent
that defines the Hero-detail view.
Notice how custom components like this mix seamlessly with native HTML in the same layouts.

Data binding

Without a framework, you would be responsible for pushing data values into the HTML controls

and turning user responses into actions and value updates.

Writing such push/pull logic by hand is tedious, error-prone,

and a nightmare to read, as any experienced jQuery programmer can attest.

Angular supports two-way data binding,

a mechanism for coordinating parts of a template with parts of a component.

Add binding markup to the template HTML to tell Angular how to connect both sides.

The following diagram shows the four forms of data binding markup.

Each form has a direction—to the DOM, from the DOM, or in both directions.

This example from the HeroListComponent template uses three of these forms:

src/app/hero-list.component.html (binding)

<li>{{hero.name}}</li>
<app-hero-detail [hero]="selectedHero"></app-hero-detail>
<li (click)="selectHero(hero)"></li>

The {{hero.name}} interpolation displays the component's hero.name property value within the <li> element.
The [hero] property binding passes the value of selectedHero from the parent HeroListComponent
to the hero property of the child HeroDetailComponent.
The (click) event binding calls the component's selectHero method
when the user clicks a hero's name.

Two-way data binding is an important fourth form

that combines property and event binding in a single notation.

Here's an example from the HeroDetailComponent template

that uses two-way data binding with the ngModel directive:

src/app/hero-detail.component.html (ngModel)

<input [(ngModel)]="hero.name">

In two-way binding, a data property value flows to the input box from the component as with property binding.

The user's changes also flow back to the component, resetting the property to the latest value, as with event binding.

Angular processes all data bindings once per JavaScript event cycle,

from the root of the application component tree through all child components.

Data binding plays an important role in communication between a template and its component,

and is also important for communication between parent and child components.

Pipes

Angular pipes let you declare display-value transformations in your template HTML.

A class with the @Pipe decorator defines a function that

transforms input values to output values for display in a view.

Angular defines various pipes, such as the date pipe and currency pipe;

for a complete list, see the Pipes API list.

You can also define new pipes.

To specify a value transformation in an HTML template, use the pipe operator ( | ):

{{interpolated_value | pipe_name}}

You can chain pipes,

sending the output of one pipe function to be transformed by another pipe function.

A pipe can also take arguments that control how it performs its transformation.

For example, you can pass the desired format to the date pipe:

<!-- Default format: output 'Jun 15, 2015'-->
 <p>Today is {{today | date}}</p>

<!-- fullDate format: output 'Monday, June 15, 2015'-->
<p>The date is {{today | date:'fullDate'}}</p>

 <!-- shortTime format: output '9:43 AM'-->
 <p>The time is {{today | date:'shortTime'}}</p>

Directives

Angular templates are dynamic.

When Angular renders them, it transforms the DOM according to the instructions given by directives.

A directive is a class with a @Directive decorator.

A component is technically a directive

- but components are so distinctive and central to Angular applications that

Angular defines the @Component decorator,

which extends the @Directive decorator with template-oriented features.

There are two kinds of directives besides components:

1. structural directives

2. attribute directives

Just as for components,

the metadata for a directive associates the class with a selector that you use to insert it into HTML.

In templates, directives typically appear within an element tag as attributes,

either by name

or as the target of an assignment

or a binding.

Structural directives

Structural directives alter layout by adding, removing, and replacing elements in DOM.

The example template uses two built-in structural directives to add application logic to how the view is rendered:

src/app/hero-list.component.html (structural)

<li *ngFor="let hero of heroes"></li>
<app-hero-detail *ngIf="selectedHero"></app-hero-detail>

*ngFor is an iterative; it tells Angular to stamp out one <li> per hero in the heroes list.
这个stamp out 用得妙啊,妙!
*ngIf is a conditional;
it includes the HeroDetail component only if a selected hero exists.

Attribute directives

Attribute directives alter the appearance or behavior of an existing element.

In templates they look like regular HTML attributes, hence the name ( 因此而得名 ).

The ngModel directive,

which implements two-way data binding,

is an example of an attribute directive.

ngModel modifies the behavior of an existing element (typically an <input>)

by setting its display value property and responding to change events.

src/app/hero-detail.component.html (ngModel)

<input [(ngModel)]="hero.name">

Angular has more pre-defined directives that

either alter the layout structure (for example, ngSwitch)

or modify aspects of DOM elements and components (for example, ngStyle and ngClass).

You can also write your own directives.

Components such as HeroListComponent are one kind of custom directive.

You can also create custom structural and attribute directives.

Introduction to services and dependency injection

Service is a broad category ( 广义的东东 ) encompassing ( 包含 ) any value, function, or feature that an app needs.

A service is typically a class with a narrow, well-defined purpose.

It should do something specific and do it well.

Angular distinguishes components from services

in order to increase modularity and reusability.

By separating a component's view-related functionality from other kinds of processing,
you can make your component classes lean and efficient.
Ideally ( 理想情况下 ), a component's job is to enable the user experience and nothing more.
It should present properties and methods for data binding,
in order to mediate between the view (rendered by the template)
and the application logic (which often includes some notion of a model).
A component should not need to define things like
how to fetch data from the server,
validate user input,
or log directly to the console.
Instead, it can delegate such tasks to services.
By defining that kind of processing task in an injectable service class,
you make it available to any component.
You can also make your app more adaptable
by injecting different providers of the same kind of service,
as appropriate in different circumstances.

Angular doesn't enforce these principles.

Angular does help you follow these principles

by making it easy to factor your application logic into services

and make those services available to components through dependency injection.

Service examples

Here's an example of a service class that logs to the browser console:

src/app/logger.service.ts (class)

export class Logger {
  log(msg: any)   { console.log(msg); }
  error(msg: any) { console.error(msg); }
  warn(msg: any)  { console.warn(msg); }
}

Services can depend on other services.

For example, here's a HeroService that depends on the Logger service,

and also uses BackendService to get heroes.

That service in turn might depend on the HttpClient service to fetch heroes asynchronously from a server.

src/app/hero.service.ts (class)

export class HeroService {
  private heroes: Hero[] = [];

  constructor(
    private backendService: BackendService,
    private logger: Logger) { }

  getHeroes() {
    this.backendService.getAll(Hero).then( (heroes: Hero[]) => {
      this.logger.log(`Fetched ${heroes.length} heroes.`);
      this.heroes.push(...heroes); // fill cache
    });
    return this.heroes;
  }
}

Dependency injection ( DI )

Components consume services; ( 这个consume用得妙啊,妙! )

that is, you can inject a service into a component,

giving the component access to that service class.

To define a class as a service in Angular,

use the @Injectabl decorator to provide the metadata

that allows Angular to inject it into a component as a dependency.

Similarly, use the @Injectable decorator to indicate that

a component or other class (such as another service, a pipe, or an NgModule) has a dependency.

A dependency doesn't have to be a service

—it could be a function, for example, or a value.

Dependency injection (often called DI) is wired into the Angular framework ( wire这个词用得妙啊,妙! )

and used everywhere to provide new components with the services or other things they need.

The injector is the main mechanism.
You don't have to create an Angular injector.
Angular creates an application-wide injector for you during the bootstrap process.
The injector maintains a container of dependency instances
that it has already created, and reuses them if possible.
A provider is a recipe for creating a dependency.
For a service, this is typically the service class itself.
For any dependency you need in your app,
you must register a provider with the app's injector,
so that the injector can use it to create new instances.

When Angular creates a new instance of a component class,

it determines which services or other dependencies that component needs

by looking at the types of its constructor parameters.

For example, the constructor of HeroListComponent needs a HeroService:

src/app/hero-list.component.ts (constructor)

constructor(private service: HeroService) { }

When Angular discovers that a component depends on a service,

it first checks if the injector already has any existing instances of that service.

If a requested service instance does not yet exist,

the injector makes one using the registered provider,

and adds it to the injector before returning the service to Angular.

When all requested services have been resolved ( 解析 ) and returned,

Angular can call the component's constructor with those services as arguments.

The process of HeroService injection looks something like this:

Providing services

You must register at least one provider of any service you are going to use.

You can register providers in modules or in components.

When you add providers to the root module,
the same instance of a service is available to all components in your app.

src/app/app.module.ts (module providers)

providers: [
  BackendService,
  HeroService,
  Logger
],

When you register a provider at the component level,
you get a new instance of the service
with each new instance of that component.
意思是就是: 为每一个组件实例,提供一个全新的service instance
At the component level,
register a service provider in the providers property of the @Component metadata:

src/app/hero-list.component.ts (component providers)

下面是组件级的service

@Component({
  selector:    'app-hero-list',
  templateUrl: './hero-list.component.html',
  providers:  [ HeroService ]
})

For more detailed information, see the Dependency Injection section.

Next steps: tools and techniques

Once you have understood the basic building blocks,

you can begin to learn more about the features and tools

that are available to help you develop and deliver Angular applications.

Angular provides a lot more features and services that are covered in this documentation.

Responsive programming tools

Lifecycle hooks:
Tap into key moments in the lifetime of a component,
from its creation to its destruction, by implementing the lifecycle hook interfaces.
Observables and event processing:
How to use observables with components and services to publish and subscribe to messages of any type,
such as user-interaction events and asynchronous operation results.

Client-server interaction tools

HTTP: Communicate with a server to get data, save data,
and invoke server-side actions with an HTTP client.
Server-side Rendering:
Angular Universal generates static application pages on the server through server-side rendering (SSR).
This allows you to run your Angular app on the server in order to improve performance
and show the first page quickly on mobile and low-powered devices,
and also facilitate ( 方便 ) web crawlers ( 网络爬虫 ).
Service Workers:
A service worker is a script that runs in the web browser
and manages caching for an application.
Service workers function as a network proxy.
They intercept outgoing HTTP requests
and can, for example, deliver a cached response if one is available.
You can significantly improve the user experience
by using a service worker to reduce dependency on the network.

Domain-specific libraries

Animations:
Animate component behavior without deep knowledge of animation techniques
or CSS with Angular's animation library.
Forms: Support complex data entry scenarios
with HTML-based validation and dirty checking.

Support for the development cycle

Testing Platform: Run unit tests on your application parts as they interact with the Angular framework.
Internationalization: Angular's internationalization ( i18n ) tools can help you make your app available in multiple languages.
Compilation: Angular provides just-in-time (JIT) compilation for the development environment,
and ahead-of-time (AOT) compilation for the production environment.
Security guidelines: Learn about Angular's built-in protections against common web-app vulnerabilities
and attacks such as cross-site scripting attacks.

Setup and deployment tools

Setup for local development: Learn how to set up a new project for development with QuickStart.
Installation: The Angular CLI, Angular applications, and Angular itself depend on features and functionality
provided by libraries that are available as npm packages.
Typescript Configuration: TypeScript is the primary language for Angular application development.
Browser support: Learn how to make your apps compatible across a wide range of browsers.
Deployment: Learn techniques for deploying your Angular application to a remote server.

未完待续,下一章节,つづく

Angular_文档_01_Architecture