Build tools have become a necessary component in the workflow for modern web applications. I have previously covered the basics of what build tools...
For further actions, you may consider blocking this person and/or reporting abuse
Hey Brian!!! Great article! Would you mind leveraging our new branding logos!? webpack.js.org/branding :-D <3
of course switching it out now.
Not sure why you mentioned npm, congrats on actually finding an article that tries to sell npm as a build tool, but even that article starts using browserify if you read any further.
If we're gonna call npm a build tool, might as well mention bash and linux too.
thanks
Don't be that guy.
One concern I have with the title of this article is the false dichotomy of "to config" vs. "to not config". The approach of some tools is zero-initial configuration, while still giving you the ability to modify the build config if you need it. So it's not always an either-or. This is how Neutrino works. neutrino.js.org/
Also check out github.com/egoist/bili
I think its worth mention the fuse-box project it falls under the same category as parcel/webpack
What about brunch? 🤔
Hey Brian,
thanks for your effort!
Brian, thanks for the article. That said I was surprised jspm wasn't included. I've been using it for quite a while for my web app Clibu. And it has had es6 module support from its beginning.
Neville
Actually never heard of jspm. Thanks for mentioning it