Using ${configDir} broken in v6+

[jozefmery]

Hi,

I have a monorepo setup, where I have a package for tsconfig.json files. I'm using the ${configDir} to define includes there, but updating to 6+ breaks the resolution, even after the fix for issue #197. The symptoms are the same though.

Reproduction in the context of a minimal React Router v7 app:

repr

Run:

• pnpm dev or pnpm build

Using v5 or running pnpm typecheck works, so the tsconfig file should be valid.

Logs:

configMismatch: {"importer":"<redacted>/repr/app/root.tsx","id":"~/foo.ts","configPath":"<redacted>\\repr\\tsconfig.json"}

[aleclarson]

We have a test for ${configDir} (which passes). https://github.com/aleclarson/vite-tsconfig-paths/tree/master/test/__fixtures__/configDir-syntax

Try reproducing the issue there.

pnpm test -t configDir

[benpsnyder]

I dug into this while working on #211 (v7 rewrite) and found the root cause.

The problem: ${configDir} support was added in tsconfck 3.1.0 (May 2024). v6 depends on tsconfck ^3.0.3, so if your lockfile resolved to 3.0.3, ${configDir} is left as a literal string in the include patterns — it never gets replaced with the actual directory. The plugin then compiles ${configDir}/**/* into a regex that can't match any real file path, producing configMismatch for every import.

I verified this directly:

tsconfck 3.0.3 → include: ["${configDir}/**/*"]      (literal, broken)
tsconfck 3.1.6 → include: ["/absolute/path/**/*"]    (resolved, works)

Workaround for v6: Force tsconfck to resolve to >=3.1.0 in your lockfile. In pnpm you can use pnpm.overrides in your root package.json:

{
  "pnpm": {
    "overrides": {
      "tsconfck": "^3.1.6"
    }
  }
}

v7 status: #211 bumps the tsconfck dependency to ^3.1.6, so this is resolved out of the box.