CuratedExecution-verifiedTypeScriptVite 8local

resolve.tsconfigPaths silently ignored in Vite 8 build (works without enabling it)

Problem

Per Vite docs, `resolve.tsconfigPaths` must be explicitly enabled to resolve tsconfig path aliases, but in Vite 8 the build command resolves them correctly even when the option is left disabled, while dev mode does not - an inconsistency between dev and build. Also affects multi-tsconfig setups (tsconfig.xxx.json) which are not recognized at all.

Solution

typescript

This was a resolver bug (not intended behavior): build mode was always resolving tsconfig paths regardless of the `resolve.tsconfigPaths` setting. Fixed by vitejs/vite PR #22695 (merged) - upgrade to the Vite release containing that PR. After the fix, explicitly set `resolve.tsconfigPaths: true` in vite.config.ts if you rely on tsconfig path aliases; do not depend on the old always-on build behavior.