There’s a new task runner around, Gulp.js, and it’s supposedly very good (haven’t had a chance to try it yet) but there are still many projects using Grunt. If you want to try out Gulp on an existing Grunt-based project, it can be tedious to start rewriting things because Gulp is imperative and based on the idea of streams while Grunt is more declarative.
grunt2gulp.js helps make the transition from Grunt to Gulp. I used the files on this blog post as a test case, and I also used a Gruntfile from a strongloop project as a test case. Both test cases are included in the examples directory.
What I like about gulp from what I saw is that it’s a wrapper around orchestrator and vinyl-fs and it’s straight-forward. Grunt is monolithic from what I’ve seen and I think moving to Gulp will be a good move over the long-term. However, I think there is still a place for a declarative sort of task configuration file.
In any case, if you’re trying to move to Gulp from Grunt, check out grunt2gulp! Feedback would be great, and patches would be awesome.
Into Frontend Web Dev? Check out some of these articles
- React.js vs Elm: building a comment box widget in Elm
- Loom, a build tool alternative to Grunt, Gulp and Webpack
- Angular 2 vs 1, a work in progress list of the differences between Angular 2 and AngularJS 1.5/1.6
2017 Update: grunt2gulp is still being used but it seems now that people are moving from Grunt and Gulp to webpack (or SystemJS or Rollup.js). Gulp is still a very cool build tool to use and I recommend that people move away from Grunt as soon as possible on to more modern tools like Gulp and Webpack and Rollup.js.