Fix auto-import when paths points to project reference redirect

[andrewbranch]

Fixes #51269

[andrewbranch]

@typescript-bot pack this

[typescript-bot]

Heya @andrewbranch, I've started to run the tarball bundle task on this PR at 4f5d243. You can monitor the build here.

[typescript-bot]

Hey @andrewbranch, I've packed this into an installable tgz. You can install it for testing by referencing it in your package.json like so:

{
    "devDependencies": {
        "typescript": "https://typescript.visualstudio.com/cf7ac146-d525-443c-b23c-0d58337efebc/_apis/build/builds/138465/artifacts?artifactName=tgz&fileId=B24E168A5F156C443B7715945540EF9C883F6507E423099809ECA2957D1C1B3702&fileName=/typescript-5.0.0-insiders.20221111.tgz"
    }
}

and then running npm install.

[Andarist]

Offtopic question: I was actually exploring using exactly this structure in one of the projects. However, I only want this because Remix doesn't allow me to alias paths - but it can infer aliases from the compilerOptions.paths.

I wonder what are the pros/cons of this structure. I guess that in this test case here it might be required to use non-relative paths as /common/ isn't actually symlinked as a monorepo package. However, when referenced projects are symlinked in node_modules, I expect this to be unnecessary and less performant. In the IDE this might be roughly the same thanks to "behind-the-scenes in-memory .d.ts generation process" but when running tsc -b this might not be able to actually leverage the generated .d.ts files as the paths map to /src/, right?

[andrewbranch]

Well, in this example paths map to dist (the original repro didn’t set a rootDir so the output is in dist/src and I kept that quirk in the test). But IIRC whether you map to the inputs or outputs of a referenced project, TypeScript understands what you’re doing and tsc will find the .d.ts outputs and the language service will find the .ts inputs.