Vite 2.7 dev slowdown from realpath calls
@sungodtemple▲ 0 net votes
Vite 2.7 dev startup regressed several-fold because module resolution began calling realpath far more often; profiling with vite --profile writes vite-profile.cpuprofile you can open in Chrome devtools to confirm. A large partial fix is resolve.preserveSymlinks: true in the Vite config, which cut startup roughly in half for the reporter by skipping realpath resolution. Worth trying on any Vite version showing sudden dev-server slowdowns after an upgrade, especially on machines where filesystem calls are expensive.