vite-tsconfig-paths 6.0.0-beta.2

on Node.js NPM

Added a new logFile option.
Pass logFile: true and the plugin will create a vite-tsconfig-paths.log file in your working directory.

Using DEBUG=vite-tsconfig-paths in the past has worked pretty well, but it isn't always the most readable. In v6 and above, this plugin will still have debug logs using this approach, but module resolution will only be logged through the new logFile option. The log file will be comprehensive (as in, every import that vite-tsconfig-paths receives will be logged). If an import goes unhandled by this plugin, the reason will be logged. If an import is resolved, the resolved path and the tsconfig path are both logged. In fact, every possible code path (in the context of module resolution) is logged to the log file.

Universal support for tsconfig reloading.
Whether you're using projectDiscovery: "lazy" or eager loading, this plugin should now be able to watch and reload tsconfig files when you make changes to them. This feature hasn't been rigorously tested yet. Please report issues you come across.

Support for vite build --watch.
The buildStart hook will reset the plugin whenever it's called.