John Gozde

This issue prevents type parameters identifiers from being found (e.g. using jscodeshift's `.find(Identifier)`) when they are attached to `CallExpression`s or `NewExpression`s. It also results in `typeParameters` not being present on...

@benjamn Any chance you could take a look at this? I've rebased my original changes on the latest master and it fixes the linked issue.

I also switched to using the `TSHasOptionalTypeParameterInstantiation` base for both `CallExpression` and `NewExpression`.

This issue manifests when `` is used inside of a `` tree in React 18.

@weidonglian True, but IMO it should still be fixed. StrictMode is intended to reveal potential issues, especially with future React versions/rendering modes and I think it's highlighting a legitimate problem...

Another point in favour of junctions: they are used by `npm` on Windows when using `npm link`, so it is already common in the Windows/node world.

@edclement, @coreybutler I'm reasonably sure that `npm link` uses junctions by default (which can be done with `mklink /J`, btw). Otherwise, linking would have to be done in an elevated...

Trying to find potentially related issues in NodeJS and this one jumped out at me: https://github.com/nodejs/node/issues/40014 And the associated V8 bug: https://bugs.chromium.org/p/v8/issues/detail?id=12198

> * Is anyone aware if this memory leak has implications beyond slowing down jest, i.e. should we hold back with updating node servers running in production? I did some...

> I'll have to look into why the number of NPM packages installed increased so much in BP4. I think it was due to the addition of the `change-case` package....