Support leading slashes in paths

[qmg-akara]

Hello, thanks for this great work!

We have some special aliases that starts with a leading slash, such as /opt/nodejs/lambda-layer and tsc successfully compiles this code however we are getting import/no-unresolved error for these aliases. When we remove the leading slash, i.e. opt/nodejs/lambda-layer, it works fine.

tsconfig.eslint.json:

{
  "compilerOptions": {
    "baseUrl": ".",
    "paths": {
      "/opt/nodejs/lambda-layer": ["./packages/lambdaLayer/src"]
    }
  },
  "include": ["**/*.ts"],
  "exclude": ["**/node_modules"]
}

error:
Unable to resolve path to module '/opt/nodejs/lambda-layer' import/no-unresolved

tsc --build builds the code successfully so I wonder if this is a bug in eslint-import-resolver-typescript or am I missing something? Thanks

[JounQin]

tsconfig-paths is used under the hood.

See also dividab/tsconfig-paths#128

[qmg-akara]

Thanks @JounQin for the prompt reply! and the link. As this is a tsconfig-paths issue I'm going to close this. Thanks

[qmg-akara]

Or I'm opening for tracking the tsconfig-paths issue, so once it is resolved, eslint-import-resolver-typescript could upgrade tsconfig-paths. Feel free to close if you think no need to keep this open.

[JounQin]

@qmg-akara You can try to use patch-package and patch tsconfig-paths by editing lib/try-path.js like https://github.com/dividab/tsconfig-paths/pull/180/files temporarily.

[qmg-akara]

Thanks @JounQin for letting me know that! I think we'll just disable import/no-unresolved for now until it is resolved. Thanks

[qmg-akara]

Hi @JounQin , looks like tsconfig-paths issue is resolved, would it be possible to update this package too? Thanks

[JounQin]

We use "tsconfig-paths": "^3.9.0", so it's free to upgrade tsconfig-paths to 3.14+ by yourself.

[qmg-akara]

Looks like there is no an official way of upgrading indirect dependencies, I have created a PR here

[JounQin]

You can delete it from yarn.lock or something else, or just reinstall this resolver.