Web apps ship JavaScript library code they never use
Web developers can pay a bundle-size cost for features they do not use, especially when a client library pulls in modules such as realtime code or dependencies that tree-shaking does not remove. That can mean larger browser downloads, and developers may need to change build setups or fork a library to work around it. The signals mainly concern Supabase JS bundle size; other requests point to adjacent JavaScript build-size frustrations.
For javaScript web developers. Mentioned from Apr 2021 to May 2025 on GitHub and Hacker News.
8 different people described this problem in 4 separate discussions.
- Indie fit
- 3.0/10
- Pain
- 5.3/10
- Frequency
- 7.9/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Professionals
- Competition
- High
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
supabase-js is currently the largest dependency of my app and I currently only use auth
nvm. i got an error on angular cli stating that realtime-js relies on common.js and thus increases bundle size. i forked supabase-js and remove realtime-js references, if someone is interested:
Build brief
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
- 6 more quotes from people who have this problem
- Current workarounds, existing solutions and risks