Re:Webpack 2.2 – Release Candidate
by tootie on Wednesday December 14, 2016 @05:49PM
(#13180444)
Every time I look at my webpack config and it's nested properties with no descriptors I yearn for Maven and it's rigorously-defined XML.
[ Parent
| on HN ]
Different strokes but I just had the severe displeasure of constructing a pom.xml for the first time and I would pay good money to never do it again.
I would infinitely prefer to use JS tooling over Java's in general so maybe that's not saying much.
POM is not exactly intuitive, but the configuration directives are at least discoverable. If you're using a decent IDE, all the config options and values work with autocomplete. It's also pretty trivial to generate an archetype for most common needs.
Webpack is practically a blank slate.
But that's more of a documentation issue rather than an xml/json issue - you could certainly have an xml file without a schema. I think it mainly shows the maturity of Maven vs webpack(which is currently working hard on documenting everything).