What's Changed

• Add provenance-enabled npm releases by @aleclarson in #224
• Support TypeScript 7 without tsconfck by @aleclarson in #223

Full Changelog: v7.0.0-alpha.1...v7.0.0-alpha.2

This release marks a major modernization of vite-tsconfig-paths, moving to the OXC and Rolldown ecosystem for significantly improved performance and a leaner dependency tree.

Special thanks to Ben Snyder (@benpsnyder) for this massive overhaul!

High-Level Changes

• OXC Resolver Integration: Replaced custom path-matching logic with oxc-resolver. This handles tsconfig paths natively in Rust, providing a high-performance resolution pipeline.
• Rolldown Ready: Added support for Rolldown-compatible resolveId hook filters. This allows skipping unnecessary JS-to-Rust boundary calls for relative imports and virtual modules on supported engines (Vite 6.3+, Rollup 4.38+, and Rolldown).
• Toolchain Modernization:
  • Switched from tsup to Rolldown for bundling, reducing transitive dependencies by over 100.
  • Migrated from Prettier to oxfmt (OXC's formatter).
  • Introduced oxlint for fast, type-aware linting.
  • Uses oxc-transform for native .d.ts generation via isolatedDeclarations.
• TypeScript 6.0: Upgraded to TypeScript 6.0 RC, including fixes for new strictness requirements and deprecations.
• Performance Wins: Benchmarks show the new implementation is approximately 1.22x faster on the plugin's own test suite and provides measurable wins in real-world AnalogJS targets.

Breaking Changes & Compatibility

• Node.js >= 18 is now required.
• Vite >= 5.0.0 is now the minimum supported version.
• .json Import Guard: The guard now applies to all resolutions (including those from paths), requiring explicit extensions for JSON files if they aren't matched by a specific pattern.
• Drop-in Replacement: Despite the internal rewrite, all existing test fixtures pass, and the plugin remains a drop-in replacement for most users.

How to try it

This is an alpha release. You can install it using the next tag:

npm install vite-tsconfig-paths@next

Features

• New importerFilter option: Provides fine-grained control over which files should have their imports resolved by this plugin. (Closes #175, #193)
• Ignore .d.ts overrides: The plugin now ignores resolutions that point to .d.ts files, avoiding issues when tsconfig is used for opt-in type overrides. (Closes #179, #180)

Performance

• Hoisted regular expressions out of the hot path in the resolver for better performance.

Internal

• Added resolvedToDeclarationFile event to the debug log file.

Note: No intentional breaking changes. Major version bump due to extensive internal refactoring; downgrade to v5 if needed.

Highlights

• On-demand tsconfig discovery via projectDiscovery: "lazy", while eager discovery remains the default.
• tsconfig/jsconfig files are watched and reloaded automatically in both modes, including during vite build --watch.
• New logFile option for per-import resolution traces (pass true for vite-tsconfig-paths.log or provide a path).
• Support for root /* aliases and other absolute-style imports.
• Support for .astro files when allowJs/loose is enabled.

Fixes

• More reliable tsconfig watching and resolver refreshes: handles lazy discovery edge cases, recreates resolvers after file changes, tolerates missing directories, and copes better with virtual importers.
• Windows path handling now normalizes drive-letter casing to avoid missed matches (#183).

Upgrade notes

• Install the stable release: pnpm add -D vite-tsconfig-paths.
• Opt into lazy discovery or logging when needed:

import tsconfigPaths from 'vite-tsconfig-paths'

export default {
  plugins: [
    tsconfigPaths({
      projectDiscovery: 'lazy',
      logFile: true,
    }),
  ],
}

• Rooted path patterns such as "/*": ["src/*"] now resolve the same way tsserver does.

• fix(windows): ensure drive letter is uppercase (#183)
• feat: add .astro to JS-like extension regex (fbbc8edb86606c612565a6672c8e0ae93f0001a0)

• Added support for /* path aliases. (#101)

• Added a new logFile option.
  Pass logFile: true and the plugin will create a vite-tsconfig-paths.log file in your working directory.

  Using DEBUG=vite-tsconfig-paths in the past has worked pretty well, but it isn't always the most readable. In v6 and above, this plugin will still have debug logs using this approach, but module resolution will only be logged through the new logFile option. The log file will be comprehensive (as in, every import that vite-tsconfig-paths receives will be logged). If an import goes unhandled by this plugin, the reason will be logged. If an import is resolved, the resolved path and the tsconfig path are both logged. In fact, every possible code path (in the context of module resolution) is logged to the log file.

• Universal support for tsconfig reloading.
  Whether you're using projectDiscovery: "lazy" or eager loading, this plugin should now be able to watch and reload tsconfig files when you make changes to them. This feature hasn't been rigorously tested yet. Please report issues you come across.

• Support for vite build --watch.
  The buildStart hook will reset the plugin whenever it's called.

• Added a new projectDiscovery option.

  When this option is set to "lazy", tsconfig files will be loaded on-demand. When an import is resolved, the parent directories of the importer are searched for tsconfig files matching the configNames array option (which defaults to ["tsconfig.json", "jsconfig.json"]).

  If using TypeScript’s project references, you can ensure they are discovered by adding the main project to the projects array option of this plugin. Though, this is only necessary if you’re referencing tsconfig files with non-standard names (e.g. "tsconfig.src.json"). Setting the projects option will not interfere with lazy project discovery.

• fix: correctly infer the paths root dir (eea1c17d0fe4ad6e3f8bc324216bc09173e3c778) (#150)

• fix: Once an importer is matched, end directory traversal (b0d8ecb9b862412e93f73b172cc0692259ce01b8)
• feat: Add vite-tsconfig-paths:resolve debug logs (7160d6e52673367a7f4766ca9023ddc1da43e5dd)
• chore: Ensure debug logs can be enabled in vitest (0dc9a8b9b0ec8657f9d6980ac33d0bc090e278ef)

• fix Windows regression introduced in v5.1.1 (#162)

• support ${configDir} syntax in include/exclude (#156)

• Add skip option for adding additional directories to be skipped when searching for tsconfig.json files (#146)
• Fix path resolution on Windows when other Vite plugins neglect to normalize the importer path before calling this.resolve in their resolveId hooks (#157)
• Allow both tsconfig.json and jsconfig.json in the same directory (4124b091607503d44b876bb4edd726667b386660)

This package is now ESM only in order to align with Vite: https://vitejs.dev/guide/migration#deprecate-cjs-node-api

If your project is using CommonJS, you can rename your Vite config to use the .mjs or .mts extension (depending on whether you use TypeScript or not). If you're not using Vite v5.0.0+, you may want to pin your dependency to v4 of this plugin.

• 353926a feat: use jsconfig.json if present (closes #22)

• 4cc78b4816eb7eea13cae878d8a4b6da8d691c27 fix: avoid breaking change from #128

• d496ea9c90c2e1159c53fc54d5e435d4316d47ee fix: forward options when calling this.resolve (#128) (thanks to @pcattori)

⚠️ This release may have broken Vite versions older than 5.0

• 8b4f6c8872bce9de5480fb7104418e77ee6fe889 feat(perf): leverage tsconfk caching to skip redundant work (#119) (thanks to @fwouts)

• 7a97869db40bf42924856bf586b615cb3003dbc7 If a tsconfig file is malformed and cannot be parsed (e.g. its extends property points to a non-existent file), an error is now logged instead of crashing the process. You can disable parsing error logs by setting ignoreConfigErrors: true in the plugin options.

• 9766de8a0dc0889800005c5c6b3f8c3954171d08 If the projects option is used, any missing tsconfig files will be silently ignored (other than a debug log, enabled with DEBUG="vite-tsconfig-paths" environment variable).

• Stop using the tsconfig-paths package It is better to let Vite handle all of the resolving, so that this plugin can be only responsible for the path mapping.

  At the same time, I am also adding the tsconfck package, which handles the loading of tsconfig.json files for us. This package is also used in Vite core (we should have Vite expose it in the future, to avoid the duplication).

  The tsconfig-paths package was previously responsible for config loading and much of the path resolving logic, but now we can ditch it! I'm also ditching the recrawl-sync package, which was used for crawling the filesystem in search of tsconfig.json files.

• Remove the extensions option Since the file resolution is delegated to Vite core, this option is no longer necessary.

• Add the parseNative option The tsconfck package has a parseNative function that's able to delegate config loading to the TypeScript compiler. If you encounter a bug in tsconfig.json file loading, you can try passing parseNative: true to see if that helps. But you should avoid enabling it otherwise, since it has a noticeable performance cost (up to 600ms roughly speaking).

• support jsconfig.json files (thanks to @MichaelDeBoey)