Andrew Branch

@nivida that already works in `--module nodenext`; you can see an example [here](https://github.com/andrewbranch/example-subpath-exports-ts-compat/blob/781b4f47ea459eea10ac66524fb9e2c882d1a3ea/examples/node_modules/package-json-redirects/package.json#L6)

@typescript-bot agrees with your guess about the cause, which is strange and definitely unintentional since there _is_ no binding pattern in the repro 🤔

Thanks. I forgot to update this issue, but we decided that the fix looked a little risky to ship in a patch when weighed against the small number of reports...

@typescript-bot bisect good v4.4.4 bad v4.5.5

That seems highly unlikely, @typescript-bot

The issue with the bisect was that the culprit commit was cherry-picked from main to release-4.5, and I only look at the timeline of commits going into main. I’m far...

Reading the description on #46599, it seems like this is expected behavior.

This isn’t a solution, but you will be probably be interested in watching #50153 (part of #50152). I’m definitely open to brainstorming good ways to resolve DT types for vendored...

My current thoughts are 1. This should Just Work™ for mapping `./node_modules/*` to `./node_modules/@types/*` at least in `--moduleResolution minimal`, but possibly in all modes? 2. But I’m interested in solving...

After thinking about it for about 30 seconds, I’m wondering if it needs to be more complicated than ```json { "compilerOptions": { "relativePaths": { "./node_modules/*": ["./node_modules/*", "./node_modules/@types/*"] } } }...