-
-
Notifications
You must be signed in to change notification settings - Fork 78.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[WIP] Transition from Grunt to Gulp #20310
Conversation
] | ||
} | ||
} | ||
}; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Extra semicolon semi
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Extra semicolon semi
It seems it's a question
but I want to know what's the reasons to move from Grunt to Gulp ? |
TBH, I'd rather move to npm scripts instead of gulp. |
We're going with a different route: #20332 |
Ok, That's fine. On Jul 20, 2016, at 15:43, Chris Rebert <[email protected]mailto:[email protected]> wrote: We're going with a different route: #20332#20332 You are receiving this because you authored the thread. |
As said in #17021 in the super ambitious nice to haves, I have transitioned from Grunt to Gulp.
Some things still need to be done and not everything works.
This is a base for the transition from Grunt to Gulp.
I have done my best to try to create all the tasks, it wan't that easy trying to find what each task does.
Also note that
grunt-saucelabs
does not have a gulp equivalent, so something will need to be thought out as an alternative.Another note, the hound config needs updating.
If anyone has any improvements, please post them here.