6 ms·
The problem with webpack, beside being very slow, is it's based on config files. Config files are brittle and very hard to understand. Spending several days s
by hsn915 5y ago
The problem with webpack, beside being very slow, is it's based on config files.
Config files are brittle and very hard to understand.
Spending several days sifting through the webpack docs and maintaining 70 lines of config files sounds like a nightmare.
Now, for esbuild, I have more lines than that for the build script, but the thing is, it's just code. The configuration part is about 10 lines. The other stuff is just programming logic.
Navigating documentation to understand what parameters something accepts is ok.
Spending time editing code is ok. It's what I do most of the time anyway.
It's tractable.
A web of configuration files is not tractable.
- Bellend 5y agoThe reason I moved away from gulp (v3?) at the time was because I considered configuration (especially an intellisense configuration) really simple as opposed to the god awful pipable javascript files gulp went for. Not sure how much that plays to my strengths though because everything I have ever used has json file configurations or object file configurations. Anyway I am definitely going to kick some tires on ESBuild, but I will just wait a while so thanks for some additional insight.
- hsn915 5y agoI never understood the point of gulp and other libraries that claim to help you write "commands". I just never used them and instead just wrote the code directly. Back in the day I was using amd.js and they had a scriptable command line utility so I just wrote a javascript file that collected all the required inputs for it and then built up the build command. (or something like that .. I don't remember the details).