vite-tsconfig-paths cannot import a basic TSconfig extends in sub-folder

[matthew-dean]

I've reduced the test case to this: https://stackblitz.com/edit/vitest-dev-vitest-oip9io?initialPath=__vitest__/

You can see that this Vite plugin fails entirely to resolve paths using TSConfig settings.

It's important to note that:

1. The app itself and TypeScript compiler work fine with this setup. Paths are always relative to their tsconfig.json file, but vite-tsconfig-paths does not account for that, and incorrectly merges path options.
2. In my actual use case, I do not have control over extending from a sub-folder nor the paths. They are auto-generated by Nuxt.

[matthew-dean]

Note also that without parseNative, the plugin failed wildly, not just on path resolution, as there are multiple tsconfig.json files that extend from others in a Nuxt setup. But even if resolving "natively", it's not actually resolving natively in the way that TypeScript actually understands those paths.

[juni0r]

@matthew-dean Did you find a fix?

[aleclarson]

In the case of @matthew-dean's reproduction, the fix is to set baseUrl in the .config/tsconfig.json file to ../ and replace the ../ prefixes in the paths array with ./ prefixes.

Example .config/tsconfig.json file

{
  "compilerOptions": {
    "target": "es2020",
    "module": "node16",
    "moduleResolution": "Node16",
    "strict": true,
    "declaration": true,
    "declarationMap": true,
    "sourceMap": true,
    "verbatimModuleSyntax": true,
    "baseUrl": "../",
    "paths": {
      "~": ["./src"],
      "~/*": ["./src/*"]
    }
  },
  "include": ["../src", "../test"],
  "exclude": ["../node_modules"]
}

This has an unfortunate side effect of allowing src/basic.js as an import specifier, due to how the baseUrl option works.

The ideal solution is for someone to contribute a fix to tsconfck that rebases paths inherited from an extended tsconfig (see here for relevant code).

[aleclarson]

Fixed in v5.1.4

[aleclarson]

Hi @mamunonweb, that's not related to this issue. Try reproducing your issue in the test suite by tweaking the paths-outside-root test fixture until it fails. You can run the test with this command:

pnpm vitest -t paths-outside-root