JavaScript, TypeScript, CoffeeScript, CSS, SASS, images - it doesn't matter to WebPack. We tend to think of modules in terms of JavaScript, but WebPack thinks of them in terms of any assets that you might want to transpile, minify and pipe to the browser. This is why I have recently become a huge fan of WebPack. I mean not a single line more than is absolutely required. So if we must exist in this world and this is the state of web tooling, I want to do as little configuration as is humanly possible. The only difference is that we're doing it with JavaScript instead of XML, which makes us somehow more evolved.
I feel like we're converging on Java where success in a web development project is 90% configuration and 10% dumb luck. No matter what you choose, you are steeped in more configuration. What I mean by that, is that once you have your task runner setup and actually working (a feat in and of itself), you then need to decide on some sort of module system for your JavaScript. To make matters worse, there is the issue of modules. Where is your Node executable? Where are your npm packages? This is mostly because task runners execute on Node, and Visual Studio is more or less agnostic of Node.
#How to run webpack with node manual
The other unfortunate thing is that Visual Studio hasn't really released anything to help with this, outside of a Task Runner Explorer package that is just an interface for the manual process. Some decent amount of knowledge around task runners (Grunt/Gulp) is required to do modern web development. Unfortunately, this is where we are right now. Which packages do I add? What was that syntax again? Is this repo's documentation out of date? LIFE HAS NO MEANING. Yeoman tried very hard to solve this problem, and did the best job of it so far, but I still want to punch myself in the throat every time I have to setup a new Grunt or Gulp file. Honestly, the amount of tooling that exists around just JavaScript and web development is hilariously out of control. Most of us are using transpilers, concatenation, uglification, directory watching, module systems and more. Unfortunately, the lack of an abstracted build system is still a problem that plagues web developers to this day. When I'm coding, I want to be able to File / New Project / ROCK AND ROLL! Someone once told me, "You should understand how MSBuild works." Should I? Isn't that what I have Visual Studio for? So I don't have to look at that XML file? Pass on that. One of the things that I've always loved about Visual Studio is how it extracts the tedium of builds.
0 kommentar(er)
