Guilherme Siquinelli 56203591b6
fix(angular): angular library was not checking to see if an import path exists (#3888)
loading child paths into an angular library was not checking to see if an import path exists, so it
generated the wrong path.
the unit tests of the angular package are working. I generated a local
release with verdaccio after the correction and generated the right children path.
2020-10-16 17:32:10 -04:00
..
2020-06-03 16:25:25 -04:00

{{links}}


Angular Plugin for Nx

{{what-is-nx}}

{{getting-started}}

? Workspace name (e.g., org name)     happyorg
? What to create in the new workspace angular    [a workspace with a single Angular application]
? Application name                    myapp
? Default stylesheet format           CSS

Serving Application

  • Run nx serve myapp to serve the newly generated application!
  • Run nx test myapp to test it.
  • Run nx e2e myapp-e2e to run e2e tests for it.

You can also use ng instead of `nx:

  • Run ng serve myapp to serve the newly generated application!
  • Run ng test myapp to test it.
  • Run ng e2e myapp-e2e to run e2e tests for it.

Adding Angular Plugin Into an Existing Workspace

You can always add the Angular plugin to an existing workspace by installing @nrwl/angular and then generating an Angular application, as follows: ng g @nrwl/angular:app myapp.

Quick Start Videos

{{resources}}