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).

v4.0.0

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

v3.5.0

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

v3.3.0

• Added ability to search for tsconfig.json files (excluding node_modules)
• Allow projects to contain not only directories, but also config paths

v3.2.0

• Respect include and exclude in compilerOptions