Webpack power

31. January 2019

I love webpack, it is a powerful open-sourced tool for front-end developer like me. I notice that every plugin I use, every other tools I use, like framework, new programming language, etc, the principial endpoint and way-of-doing is the same.

And maybe what is more important is of course, the user experience at the end – coupled together with fast and easy development.

Well, without going into deep to that philosophical programming question, I love it because at the end of the day, I always want to use a single file Javascript and CSS most of the time. I want to use cutting-edge technology most of the time. I want to use cool imports exports, Typescript, Promises, and new plugins everyday. And dealing with polyfills, managing versions of it, is always a mess. Yarn/Npm helps of course, compiling and managing it from one point and auto-updating it helps making development fun and fast again.

Now you can concentrate on what is important: Logical, Analytical, Code Structuring, and of course spends the next hour searching the name for a variable you will change again in a month, now that the purpose of the variable changed or you just understant it better now.

Set up webpack.config.js, follow most tutorials, set a base.js or a centralized js file to import it in order, and it will understand SASS ordering, mixins, and it could also do dynamic loading of Styles depended on components or inclusion in the javascript file.

I love it.