Releases: aleclarson/vite-tsconfig-paths
v4.2.0
v4.1.0
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 therecrawl-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
Thetsconfck
package has aparseNative
function that's able to delegate config loading to the TypeScript compiler. If you encounter a bug intsconfig.json
file loading, you can try passingparseNative: 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
andexclude
in compilerOptions
v3.1.0
- Support
baseUrl
withoutpaths