08aa54e1d9
The CLI app is now checked in, rather than generated dynamically with `ng new`. This loses some assertion power, but gains hermeticity. It also checks in lock files for all integration tests, avoiding floating version numbers. We'll need another place to integration test between changes in the various repositories - but the angular/angular PR-blocking status is not the right place to do this. PR Close #21555 |
||
|---|---|---|
| .. | ||
| e2e | ||
| src | ||
| .angular-cli.json | ||
| .editorconfig | ||
| README.md | ||
| karma.conf.js | ||
| package.json | ||
| protractor.conf.js | ||
| tsconfig.json | ||
| tslint.json | ||
| yarn.lock | ||
README.md
CliHelloWorld
This project was generated with Angular CLI version 1.6.6.
Development server
Run ng serve for a dev server. Navigate to http://localhost:4200/. The app will automatically reload if you change any of the source files.
Code scaffolding
Run ng generate component component-name to generate a new component. You can also use ng generate directive|pipe|service|class|guard|interface|enum|module.
Build
Run ng build to build the project. The build artifacts will be stored in the dist/ directory. Use the -prod flag for a production build.
Running unit tests
Run ng test to execute the unit tests via Karma.
Running end-to-end tests
Run ng e2e to execute the end-to-end tests via Protractor.
Further help
To get more help on the Angular CLI use ng help or go check out the Angular CLI README.