v4.0.0 mega thread

[aleclarson]

pnpm i vite-tsconfig-paths@next

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

Fixes #54
Closes #73
Probably fixes #63
Probably fixes #68
Probably fixes #71

Bugs down here 👇

I don't expect there to be bugs, but we don't currently have an extensive test suite, so it's possible. If you find any, let me know and (if you're feeling extra generous) open a PR with a reproduction in the ./demo folder.

• Regression: The tsconfck package doesn't support jsconfig.json files, so vite-tsconfig-paths has lost the support that was added in v3. See Support jsconfig.json #22

[aleclarson]

If anyone wants to help update the test suite for v4, please see #81.

[aleclarson]

Seems there were two bugs. Please try v4.0.1

• A tsconfig file with references array is now used again (unless the files property is explicitly an empty array)
• The include/exclude patterns are compiled correctly again

[DreierF]

@aleclarson I can at least confirm that 4.0.1 fixed our concrete instance of the problem. Thanks for the fast update!

[aniravi24]

@aleclarson sorry for the delay, looks like everyone else got to this quickly and discovered the issue (thank you!) I can also confirm 4.0.1 fixed the specific issue I was having.

[mandarini]

@aniravi24 @DreierF for Nx:

• To work with 4.0.0 you can remove the projects: ['tsconfig.base.json'] from the plugin in your vite.config.ts files
• To work with 4.0.1 you still need the projects array

I put in a PR to address that. Other than this, it should work as expected.

[memark]

It would be great if the Releases page were updated with information about this new major version
https://github.com/aleclarson/vite-tsconfig-paths/releases

[aleclarson]

Please try v4.0.3 if you're on Windows. Thanks to @joshwooding

[alonando]

v4.0.3 is working on Windows with latest vite. Thanks @aleclarson & @joshwooding!

[ahnpnl]

Hi, it'd be nice if GH release page is up-to-date with release tags as well as changelog is mentioned somewhere.

[burtek]

Would it be possible to have this work also with vitest.mock? Right now the alaises from compilerOptions.paths don't work