Tianyi Cui 5202da1581 Document why vite-tsconfig-paths can't be replaced by resolve.tsconfigPaths ...

Vite >=8 warns the plugin is replaceable by the native experimental
resolve.tsconfigPaths option. It isn't for this repo: the native option
applies the nearest tsconfig.json's own paths per importing file, while
our paths map lives only in the root tsconfig — per-workspace tsconfigs
under packages/* and vendor/* have none, so native resolution falls
through to package.json exports (lib/, absent until yarn build) and
every unbuilt test import fails (verified on vite 8.0.16/vitest 4.1.8).

2026-06-11 23:24:41 +08:00

2.0 KiB

Raw Blame History

View Raw