Doesn't work with project reference when same path is configured to difference packages.

Let’s say there is a directory tree like this.

packages
  └── foo
  │   ├── src
  │   │   ├── hello.ts
  │   │   └── index.ts
  │   └── tsconfig.json
  └── bar
      ├── src
      │   ├── hi.ts
      │   └── index.ts
      └── tsconfig.json

And each file is like these.

// packages/foo/src/index.ts
import { hello } from '~/hello' // intended to import './hello'

export const helloworld = () => {
  hello('world')
}

// packages/foo/tsconfig.json
{
  "compilerOptions": {
    "paths": {
      "~/*": ["src/*"],
    }
  }
}

// packages/bar/src/index.ts
import { helloworld } from '@monorepo/foo'
import { hi } from '~/hi' // Same as importing './hi'

hi('there')
helloworld()

// packages/bar/tsconfig.json
{
  "compilerOptions": {
    "paths": {
      "~/*": ["src/*"],
      "@monorepo/*": [ "../*/src/" ]
    }
  },
  "references": [
    { "path": "../foo/tsconfig.json", "prepend": false }
  ]
}

There are two different packages foo and bar in monorepo. They use the same path ~ internally. Each package is developed by different teams independently. Thus, the consumer(bar) doesn’t know whether the dependency(foo) configures ~ as its path (And it shouldn’t care as well!).

So a developer of bar runs npx ts-node -r tsconfig-paths/register src/index.ts in packages/bar. But it fails with the error message like this.

⨯ Unable to compile TypeScript:
../foo/src/index.ts:4:23 - error TS2307: Cannot find module '~/hello' or its corresponding type declarations.

4 import { hello } from '~/hello'
                        ~~~~~~~~~

This happens because two packages use the same path internally. I expected tsconfig-paths fully respects typescript project reference feature, but it seems not.

How do you think this can be resolved?

Thanks.

[xcfox]

I’m having the same problem, I’m currently using tsc-alias as an alternative.

[thefakequake]

Any updates on fixing this?