3 ms·
tl;dr: The author meant to say "Use Browserify instead of Grunt/Gulp" but then got all confused and wrote some unrelated stuff about how npm has a case..esac st
by skrebbel 12y ago
tl;dr: The author meant to say "Use Browserify instead of Grunt/Gulp" but then got all confused and wrote some unrelated stuff about how npm has a case..esac statement built in.
While we're at the subject, might I suggest using webpack instead of browserify? It's roughly the same, but less buggy.
- Kiro 12y agoHow is Browserify/Webpack a replacement for Grunt/Gulp? Genuine question.
- Guillaume86 12y agoThey have their own plugin/watching systems, I'm trying webpack on a project and I'm just starting it with a "npm run" command.
- lerouxb 12y agoIt isn't a replacement for Grunt/Gulp. It is a replacement for browserify or perhaps require.js. It builds your javascript and css (and images!) into one or more bundles which does overlap with what people often use grunt for. In my experience it generally obviates the need for grunt because what's left to do once you've packaged and minified your js, css and images and you have your source maps, etc.? I suppose the rest can be done with npm scripts, but simple tasks like running tests could even be done from bash or a makefile anyway. Here's a good recent presentation on webpack: http://adrianrossouw.github.io/webpack-uber-alles/ http://adrianrossouw.github.io/webpack-uber-alles/
- mushishi 12y agoWhat are the most serious bugs in browserify?