* fix(backend): skip node if there is no associated TViewData The code was assuming that the TViewData item at the same index as the node in LView would contain a data entry. This value can be `null` (which is the case in our app), which causes a catastrophic failure in the dev tool. By checking for null, the node is skipped because it cannot determine the associated component or directive and the dev tool does not die. fixes issue rangle/angular-devtools#801 * chore: style tweak - add early return to avoid nesting |
||
|---|---|---|
| .. | ||
| src | ||
| karma.conf.js | ||
| ng-package.json | ||
| package.json | ||
| README.md | ||
| tsconfig.lib.json | ||
| tsconfig.spec.json | ||
| 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.