Maksym Kobieliev

I should not be writing this, but. It's so frustrating that the official angular team does not pay any attention to features that are so obvious, so desired, (seemingly) easy...

I'm facing exactly the same issue! (And it took me a few days to trace it down!). The issue only happens with Jest (not with Jasmine/Karma) and only if using...

And btw, if you run `npx ngcc`, the error message (`Can't resolve all parameters for AppComponent: (?).`) gets replaced with ``` This constructor is not compatible with Angular Dependency Injection...

Here's a simplified reproduction repo: https://github.com/Maximaximum/jest-angular-namespace-import-bug

I've just checked and the issue is reproducible with Angular v11 as well. @thymikee @ahnpnl @wtho Is there anything I could do to help resolve this issue? The suggested workaround...

@ahnpnl As I have mentioned above, in some cases the workaround is not an option at all

Fwiw, in the title of this issue "exported" should be replaced with "imported", because it's not the export syntax, but the import syntax that causes the issue

FWIW I'm now trying to use the 2nd workaround suggested by @ahnpnl. But what drastically complicates things even more is that I'm having an `nx` workspace with about 20 different...

I can't find documentation about configuring the output folder here https://angular.io/guide/angular-compiler-options. Does `ng build` do the same thing as `ngc`? Should we run jest against the bundled files located in...

@ahnpnl I don't know about the exact use cases of the other folks here, but in my specific case I have dozens of auto-generated files containing namespaced imports. Adding an...