445fbf81fd
Previously devtools used a nested workspace for its bazel configurations. This meant framework dependencies were consumed via npm. Now devtools is part of the root bazel directory that all other files in this codebase fall under. This allows us to build devtools using local angular packages, removing the need to consume these dependencies with npn. This is useful because we no longer have to update these dependencies with an automated tool like renovate, and our CI tests will always run against the most up to date framework packages. |
||
|---|---|---|
| .. | ||
| src | ||
| BUILD.bazel | ||
| index.ts | ||
| README.md | ||
| tslint.json | ||
NgDevtoolsBackend
This library was generated with Angular CLI version 8.0.0.
Code scaffolding
Run ng generate component component-name --project ng-devtools-backend to generate a new component. You can also use ng generate directive|pipe|service|class|guard|interface|enum|module --project ng-devtools-backend.
Note: Don't forget to add
--project ng-devtools-backendor else it will be added to the default project in yourangular.jsonfile.
Build
Run ng build ng-devtools-backend to build the project. The build artifacts will be stored in the dist/ directory.
Publishing
After building your library with ng build ng-devtools-backend, go to the dist folder cd dist/ng-devtools-backend and run npm publish.
Running unit tests
Run ng test ng-devtools-backend to execute the unit tests via Karma.
Further help
To get more help on the Angular CLI use ng help or go check out the Angular CLI README.