Denis Bendrikov

@lil5 *TLDR*: sometimes "just update dependencies" is not an option because of the support policy. If we take *webpack* as an example of a big package with dependencies that should...

In the meantime are there any lifehacks on how we can currently debug the DI? Something like console.log'ing all instantiated services for a module will be helpful

Have a similar use case where I have a **3rd party library** that uses `APP_INITIALIZER` to init itself which is not working for lazy loaded feature modules. I understand that...

``` js import angularFilter from 'angular-filter'; export default angular.module('app', [ angularFilter ]) .name; ``` works just fine

https://www.npmjs.com/package/audit-ci is another pretty popular alternative solution for this problem. Dropping it here to give more info for inspiration.

Added PR to fix that

@hitendra-ap so my PR is here https://github.com/litixsoft/karma-mocha-reporter/pull/109 but there are some failed tests that someone should take a look at. It is up to the maintainer what to do with...

Added CI-related fix to #109 Now it's green 🟢

Assuming that: * this project is very popular (213k downloads per week https://www.npmjs.com/package/karma-mocha-reporter ) * PR with a fix is in place #109 * tests are green I hope that...

According to CI results, I see that node 6, 7, 8 jobs didn't even run: https://app.travis-ci.com/github/litixsoft/karma-mocha-reporter/jobs/549146573#L292 Node 4 and 5 jobs failed because it can't install deps (missing `package-lock.json` pays...