Monorepo developers lose fast feedback on linked package changes
Developers building an app alongside local libraries in a JavaScript or TypeScript monorepo can’t reliably see package changes in the app without restarting, rebuilding, or accepting a full-page refresh. In Vite setups, getting linked packages watched and their source used instead of built output can require confusing configuration; developers report trying workarounds or spending a day setting things up. The strongest opportunity is a focused tool for this Vite monorepo workflow, rather than a universal hot-reload product.
For frontend developers building apps and packages in monorepos. Mentioned from Oct 2019 to Nov 2024 on GitHub.
10 different people described this problem in 4 separate discussions.
- Indie fit
- 4.0/10
- Pain
- 5.6/10
- Frequency
- 8.6/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Professionals
- Competition
- Medium
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
Since most of my code is in the libraries, not the app, this means I'll have to reboot constantly, which would seem to defeat the purpose of Vite
I spent a day setting up an nx/pnpm monorepo with a Vite TS lib mode template (for shipping npm packages), started building a complex project on top, and just assumed hot reloading wasn't working because I'd misconfigured something which could be easily fixed later
See what to build and who will buy it
- 2 product ideas with the smallest useful version and pricing
- 4 places to find your first customers
- 8 more quotes from people who have this problem
- Current workarounds, existing solutions and risks