Joost Koehoorn

> > Since the above linked issue was closed we can track the progress here https://github.com/orgs/angular/projects/2 > > @JoostK I'm interested in when this linker will be available and if...

> Using the latest `yarn 3.2.0-rc.11` and `@angular/cli-13.2.0-next` versions, this error message appears when running `yarn ng build`: > > ``` > An unhandled exception occurred: The requested module '@angular/compiler'...

> > ``` > > Error: Failed to initialize Angular compilation - Cannot locate the 'node_modules' directory. > > > > ✖ Failed to compile. > > ``` > >...

Moving to the CLI repo as this is a bug in incremental type-checking and not observed with just `ngc`.

A quick update after debugging through the incremental type-checking logic: this issue occurs due to how TypeScript's builder APIs for incremental diagnostics computations fail to report indirectly affected files as...

The same issue also occurs for the more common pattern of having indirect property accesses and changing a nested property's signature; we're only recomputing typecheck results for the affected files...

This is caused by https://github.com/facebook/jest/issues/3552. I recently experienced the same problem after adding a 9th testsuite on a quad-core hyperthreaded machine, therefore having 8 threads, and that let me down...

> Btw, sorry if it's kind of a noob question, do you know a means to find which precise bit of code makes a Jest test suite hang? @bhubr It's...

@tommoor Yeah, the `createRequire` workaround broke due to facebook/jest#9469, which the workaround was actively exploiting to break out of the sandbox. We have switched to the first workaround I described...

> @JoostK you have a private fork of Jest just for this? 😭 Nope just patching `node_modules` in a `postinstall` hook (not using Yarn pnp nor pnpm)