Michael Kriese

Having trouble using `ngcc-jest-processor`. If i run `ngcc` after install , all jest esm tests are working fine, but when only using `ngcc-jest-processor` import, most tests fail since `[email protected]` ```...

yes, cleared local jest cache seems to fix my local tests, but having issues on ci. it's running inside ephemeral docker containers. Only the workspace is held but there is...

it's getting more strange. running it on ci fails with same error. when i then run the same docker image and jest command, it succeeds as it does locally. BTW:...

i think it's not an nx issue, as i'm running jest directly. I got it back working. I exclude the `tslib` `moduleNameMapper` and set `importHelpers=false`

This is the tslib diff from v2.3.0 to v2.3.1. I'm not sure how this small change can cause those big issues 🤔 https://app.renovatebot.com/package-diff?name=tslib&from=2.3.0&to=2.3.1

> I just corrected ESM tests in `examples` of this repo but couldn’t see the issue like yours, see https://github.com/thymikee/jest-preset-angular/actions/runs/1257005889 Our examples don’t have `nx` Your tests use `[email protected]` and...

I would like to test, but i get errors with babel *ts-jest*  *babel* I get errors like: `Can't resolve all parameters for ...: (?).`  babel is a lot...

looks like it is always the same class `MyHandler` which is used to provide a service. I hope this is enough to reproduce. Technically I'm using a `nrwl` workspace with...

@wtho Next bug wtho/jpa-babel-bug#2

found workarounds for the bugs, here are the new timings:  second run