Webpack has an enormous community of third-party plugins, it would be very hard to do something similar with e.g. Go or Zig.
Webpack has an enormous community of third-party plugins, it would be very hard to do something similar with e.g. Go or Zig.
The webpack ecosystem on the other hand is it’s own OS.
I’ve heard several folks say that about Kubernetes, but in my experience the *nix core always resurfaces the second things get weird.
NPM has done a pretty great job of showing everyone else what to avoid doing.
The mere mention of “web pack” sends most of the FE devs I’ve met into borderline trauma flashbacks.
There’s seemingly half a dozen package managements tools, some of which also seem to be compilers? There’s also bundlers, but again some of these seem integrated. Half of the frameworks seem to ship their own tools?
Go programs start at 20MB. The Go AWS Terraform provider is something like 300MB.
A massive amount of the complexity/difficulty in webdev build tools space has to with optimizing delivery sizes on the web platform.
Node.js tooling is straightforward comparatively.