* rangle/angular-devtools#13 - Highlight from the component tree to the application * rangle/angular-devtools#13 - Highlight from the application to the component tree when using inspector * Fixes on broken unit tests + added all files to coverage reports * Setting test default to always generate coverage report * rangle/angular-devtools#13 - Added basic test for component inspector * feat(frontend): Moving component hover to tree to avoid passing messageBus rangle/angular-devtools#13 * feat(frontend): Sync hover from inspector to component tree rangle/angular-devtools#13 * feat(frontend): Rename function to retrieve ElementID from native element * feat(frontend): Use separate handler to unhighlight from component instead of using highlight without ID * feat(frontend): de-coupling inspector from the message bus * feat(frontend): fix unit tests
1 KiB
ng-devtools
This library was generated with Angular CLI version 9.0.0-rc.5.
Code scaffolding
Run ng generate component component-name --project ng-devtools to generate a new component. You can also use ng generate directive|pipe|service|class|guard|interface|enum|module --project ng-devtools.
Note: Don't forget to add
--project ng-devtoolsor else it will be added to the default project in yourangular.jsonfile.
Build
Run ng build ng-devtools to build the project. The build artifacts will be stored in the dist/ directory.
Publishing
After building your library with ng build ng-devtools, go to the dist folder cd dist/ng-devtools and run npm publish.
Running unit tests
Run ng test ng-devtools 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.