Previously we were using sass import rules to bring in material and other styling.
Now we are using the use rule and have switched over to the new angular material theming API
1. On scroll event we can very aggressively request updates. Although we have throttling logic, it still can be quite a heavy operation in the front end. Here we introduce 50ms throttling.
2. Do not produce `vendorChunk` in development (and production) modes.
* build: set latest SHA commit as system environment variable for chrome build
* build: set latest SHA commit as sys variable for demo build
* feat: create application environment abstraction to reference environment variables inside the ng-devtools library
* test: fix devtools component test
* 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
Currently, we don't inject `runtime.js` because we collide with the `runtime.js` of the host Angular application. This creates problems with non-Angular apps which don't use the same app bundling and the `backend.js` does not execute. This PR renames the runtime function to `___ngDevToolsRuntime`, which fixes the issue.
Additionally, since we support only Chrome this PR also drops differential bundling. We support the last two major versions of Chrome (look at `browserlist`), but if users require, we can easily extend the set of supported browsers.
Lastly, to have predictable file names, this PR also drops the hash suffix in the `shell-chrome` project.
