Switch entirely to gulp
See original GitHub issueOur build process sort of resembles Frankenstein’s monster at this point. My bad. We shouldn’t shell out to gulp from grunt and move utils out to fbjs
.
@zertosh is already working on this.
Issue Analytics
- State:
- Created 8 years ago
- Comments:11 (9 by maintainers)
Top Results From Across the Web
Switching to Gulp 4 - Webstoemp
Instead of the traditional gulp.task we all use with version 3 to define our tasks, I use simple named functions with no dependencies....
Read more >Switching from Gulp to Webpack - Stack Overflow
The concepts of Gulp and Webpack are quite different: You tell Gulp how to put front-end code together step-by-step, but you tell Webpack ......
Read more >How to Upgrade to Gulp 4 - Create default, parallel ... - YouTube
Your browser can't play this video. Learn more. Switch camera.
Read more >The Complete-Ish Guide to Upgrading to Gulp 4
Gulp 4 isn't officially released at time of publishing, but don't let that stop you from being prepared with this handy guide.
Read more >How to switch from Gulp to Webpack: a tutorial to get you started
Gulp and Webpack are two different tools intended for totally different things. Webpack is used mainly for taking your modularized ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Thanks @maxdeviant for your work on this - the build system definitely could benefit from improvement. @gaearon and @trueadm are working on rewriting it to eliminate both Gulp and Grunt in favor of Rollup, and that will close this issue.
Both Grunt and Gulp are gone with #9327. They shan’t be missed