3 ms·
You don't need to deal with the configuration for 80% of the use cases. If you need something custom, it's a good investment to learn the tool you are depending
by egeozcan 8y ago
You don't need to deal with the configuration for 80% of the use cases. If you need something custom, it's a good investment to learn the tool you are depending, and I don't think it's inscrutable: https://webpack.js.org/concepts/ https://webpack.js.org/concepts/
- dmitriid 8y agoConcepts don't describe how to string together four conflicting plugins together just to get predictable caching, for example. There's only so many hours in the day. There are better things in life than to fight a build tool.
- egeozcan 8y agoYou don't have to. Just don't use those plug-ins? If you do need that functionality, it makes sense to "fight the build tool" a bit (or just go through the docs, they really aren't as bad as you say). I personally always found a solution with Webpack. I find this amazing for a tool which is so young and written in a language without static types.