Unable to resolve modules when using yarn's PnP linker

[meriouma]

This is a breaking change in v3. Trying to run eslint with eslint-import-resolver-typescript@3+ yields multiple
error Resolve error: File '@equisoft/typescript-config/tsconfig.standards.json' not found.
4:15 error Unable to resolve path to module './some-module

Reproduction branch : https://github.com/kronostechnologies/tax-ca/tree/get-tsconfig-issue
Steps :

• yarn install
• yarn eslint

I believe the issue is caused by the change from tsconfig-paths to get-tsconfig (privatenumber/get-tsconfig#26)

[JounQin]

If you already know it's an issue from get-tsconfig, then you don't need to raise this issue?

[meriouma]

To document this package doesn't work anymore when using yarn PnP and extending a tsconfig from a dependency?

[JounQin]

It depends on get-tsconfig, and you can help to support that.

And I've documented use get-tsconfig to replace tsconfig-paths in v3, and that's why it is a major version.

[JounQin]

I noticed you raised privatenumber/get-tsconfig#27, but you just gave up by closing the PR.

Personally I don't use yarn pnp, you need provide a reproduction for get-tsconfig, so that it helps and saves all of our time.

By the mean time, you can still use v2 as workaround for now.

[JounQin]

Although this is clearly be a bug from upstream, but I'd like to fix it on our side first, because it should not be so tough because we're already using enhanced-resolve, I'll work on a fix soon.

[JounQin]

#133

After digging, I found it still should be fixed in get-tsconfig because we have no access to extends field in tsconfig.json.

@meriouma If you are going to fix that issue, I'll just leave it as-is, or I might work on a fix for get-tsconfig instead.

[JounQin]

@meriouma eslint-import-resolver-typescript@3.2.2 has been released with PnP support!