Vite

Raised as a usability problem by 9 people on Hacker News over 5 years (2022–2026), in 7 threads.

People raised many different problems with Vite, but no single problem has yet been raised by 3 people in 3 different months and threads.

Unreviewed issues were grouped by machine: Claude Haiku labelled each comment as a usability complaint, named what it's about and summed up the problem in a line, and a small model grouped similar problems. Nobody has checked them by hand. Expect mistakes.

The newest 9 complaints

Config for treating .js files as JSX was undiscoverable; docs insufficient to figure it out2026-03-13
Creates dozens of files and hundreds of config options even for simple pages2025-02-15
Console logs don't show in the IDE when running Vite with npm run dev2024-10-17
Virtual modules and dev/production differences are hard to understand and debug2024-05-10
Config is scattered and opaque, so non-standard setups are trial-and-error2024-05-04
Full page refreshes take about 4 seconds, slower than Webpack2022-07-03
After hot reload, line numbers and breakpoints no longer line up, so debugging is unreliable2022-07-03
Tooling plugins stacked from older projects break the editor, and scaffolds only work 95%2022-07-03
Setting up production build failed with polyfill and tsconfig errors, requiring trial and error2022-04-26