v5.1.2

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

v5.1.1

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

v5.1.0

• 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.0

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.

v4.3.0

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

v4.2.3

• 4cc78b4 fix: avoid breaking change from #128

v4.2.2

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

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

v4.2.1

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

v4.2.0

• 7a97869 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.

v4.1.0

• 9766de8 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).