unstale

npm / vite-tsconfig-paths

vite-tsconfig-paths

What changed in vite-tsconfig-paths 5 to 6, from its official release notes, upgrade guides and advisories. Sources checked 2026-10-23.

1 breaking3 new APIs and options1 performance2 behavior and defaults1 tooling2 fixes and other

See which of these apply to your code, ranked, in your agent:

npx @unstale/cli init

@unstale/cli 0.2.3 on npm

vite-tsconfig-paths 69 changes

New APIs and options 3

  • Provides fine-grained control over which files have their imports resolved by the plugin.

    6.1.0release notes

  • Adds per-import resolution traces; pass true to write to vite-tsconfig-paths.log or provide a path.

    6.0.0release notes

  • Adds lazy tsconfig discovery via projectDiscovery: "lazy"; eager discovery remains the default.

    6.0.0release notes

Performance 1

  • Regular expressions are hoisted out of the resolver's hot path for better performance.

    6.1.0release notes

Behavior and default changes 2

  • Root /* aliases and other absolute-style imports are supported and resolve the same way tsserver does.

    6.0.0release notes

  • tsconfig and jsconfig files are watched and reloaded automatically in both discovery modes, including during vite build --watch.

    6.0.0release notes

Tooling 1

  • Supports .astro files when allowJs or loose is enabled.

    6.0.0release notes

Fixes and other changes 2

  • The plugin ignores resolutions that point to .d.ts files, avoiding issues when tsconfig is used for opt-in type overrides.

    6.1.0release notes

  • Normalizes drive-letter casing to avoid missed matches on Windows.

    6.0.0release notes

vite-tsconfig-paths 51 changes

Breaking changes 1

  • The package is now ESM only. CommonJS projects can rename their Vite config to .mjs or .mts; projects not using Vite 5.0.0+ may pin this plugin to v4.

    5.0.0release notes