mirror of
https://github.com/angular/angular-cli.git
synced 2025-05-17 11:03:53 +08:00
beb7070ac8
Since `NGCC` is non incremental and in library projects we have the original TS sources we don't need to build a library using the `VE` and transform it using `NGCC`. Instead we can build the library using `NGTSC` (Ivy) directly as this enables faster incremental compilations and a better development experience. Libraries now have a `production` configuration, which enabled `VE` compilations. As it is not recommended to publish NGTSC (Ivy) built libraries to NPM repositories, since Ivy libraries are not backwards compatible with the legacy View Engine.
# <%= classify(name) %> This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version <%= angularLatestVersion %>. ## Code scaffolding Run `ng generate component component-name --project <%= name %>` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module --project <%= name %>`. > Note: Don't forget to add `--project <%= name %>` or else it will be added to the default project in your `angular.json` file. ## Build Run `ng build <%= name %>` to build the project. The build artifacts will be stored in the `dist/` directory. ## Publishing After building your library with `ng build <%= name %>`, go to the dist folder `cd dist/<%= dasherize(name) %>` and run `npm publish`. ## Running unit tests Run `ng test <%= name %>` to execute the unit tests via [Karma](https://karma-runner.github.io). ## Further help To get more help on the Angular CLI use `ng help` or go check out the [Angular CLI README](https://github.com/angular/angular-cli/blob/master/README.md).