58 minutes ago · 10 min read1902 words · Tech · hide

The goal is light-build, not no-build You npm install a package (e.g. vue), you write import { createApp } from "vue", and it works — as long as there is a bundler in between. Without one, the browser has no idea what "vue" is: it only understands URLs, and node_modules/ was never meant to be deployed. So even the simplest project ends up needing a bundler, only so it can use dependencies instead of reinventing the wheel. But bundlers add a significant tax. They process every single file, introduce several layers of abstraction between source and deployment, and these abstractions often leak: things that work fine in the browser can break in the build. Earlier this year, I published Web dependencies are broken: Can we fix them? that discusses this from a platform architecture perspective. Besides the architectural concerns, the complexity is an active developer pain point: in State of JS 2025, “Managing Dependencies” was the 3rd biggest pain point, and “Build tools” were 6th. However,…

Commenting on Bubbles has been removed. Why? If you want to talk about this post, write to the author, use the comments on their blog if it has them, or reply with a "RE:" post on your own blog. Suggestions? feedback@bubbles.town