Switching to Gulp #108
Switching to Gulp #108
Conversation
|
I'm totally in favor of gulp +1 |
|
@clone1018 it can be merged already then. The next step will be to just gradually improve linter and move build stuff from Grunt. I just don't want to mix too much into single PR. |
|
How did this never get merged? Rebasing ... |
Perhaps it will be able to show line number like Grunt task does
npm remove gulp-jshint --save
npm remove jshint-stylish --save
npm install gulp-eslint --save
It appears that JSON is not valid a JavaScript, so it
probably needs a separate checker.
|
The build is green, though upon inspection, linting fails with 33 errors. We should:
|
|
@techtonik Wanna pick up with this? |
|
@whit537, is @techtonik no longer an active contributor? |
|
Seems that way. Happy to have @techtonik or someone else pick up with this PR. |
|
I'll tentatively volunteer. I can't commit to a time frame yet (I am easing back into things slowly), so if someone else steps forward before I get to this I won't mind. |
|
Because of DalekJS, I can not update grunt and its dependencies, so I resurrected the branch to switch to gulp dependencies, but then I realized that the problem is in DalekJS. It is not updated anymore, and while its syntax is great, we need to switch to alternative. |
I propose a gradual transition from Grunt to Gulp, so that we can have a history of two build systems running in parallel and compare them.