Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Dec 15, 2025

This PR contains the following updates:

Package Change Age Confidence
vite-tsconfig-paths 4.3.26.1.1 age confidence

Release Notes

aleclarson/vite-tsconfig-paths (vite-tsconfig-paths)

v6.1.1

Compare Source

v6.1.0

Compare Source

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.

v6.0.5

Compare Source

v6.0.4

Compare Source

v6.0.3

Compare Source

v6.0.2

Compare Source

v6.0.1

Compare Source

v6.0.0

Compare Source

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.

v5.1.4

Compare Source

v5.1.3

Compare Source

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

v5.1.2

Compare Source

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

v5.1.1

Compare Source

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

v5.1.0

Compare Source

  • 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 (4124b09)

v5.0.1

Compare Source

v5.0.0

Compare Source

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.


Configuration

📅 Schedule: Branch creation - "before 7am on Monday" in timezone Canada/Eastern, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot requested a review from V-ed as a code owner December 15, 2025 10:58
@renovate renovate bot added the dependencies Pull requests that update a dependency file label Dec 15, 2025
@renovate
Copy link
Contributor Author

renovate bot commented Dec 15, 2025

Branch automerge failure

This PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.


  • Branch has one or more failed status checks

@renovate renovate bot force-pushed the renovate/vite-tsconfig-paths-6.x branch 2 times, most recently from c11fa1f to ab44572 Compare December 18, 2025 13:31
@renovate renovate bot force-pushed the renovate/vite-tsconfig-paths-6.x branch from ab44572 to 4b05121 Compare January 9, 2026 22:05
@renovate renovate bot force-pushed the renovate/vite-tsconfig-paths-6.x branch 3 times, most recently from c11bfe7 to de09672 Compare January 26, 2026 13:38
@renovate renovate bot force-pushed the renovate/vite-tsconfig-paths-6.x branch 2 times, most recently from e8dd8fe to 839e6d0 Compare February 9, 2026 13:07
@renovate renovate bot force-pushed the renovate/vite-tsconfig-paths-6.x branch from 839e6d0 to 0816b41 Compare February 12, 2026 02:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants