Open pablorsk opened 7 years ago
Temporal solution: replace, on package.json, this:
"gulp": "gulpjs/gulp#4ed9a4a3275559c73a396eff7e1fde3824951ebb",
for this:
"gulp": "gulpjs/gulp#3f5aba28718dc19e4bf600fb88f128158ff2ff83",
npm install --save-dev gulpjs/gulp#4.0
Is there any specific reason for mentioning gulp and gulp-hub package versions in the below format: "gulp": "gulpjs/gulp#4ed9a4a3275559c73a396eff7e1fde3824951ebb", "gulp-hub": "frankwallis/gulp-hub#d461b9c700df9010d0a8694e4af1fb96d9f38bf4",
All other dependency versions are in caret pattern, like ^1.2.0, Can I use caret range pattern for gulp and gulp-hub packages in my angular 1 project which is generated using fountain.js
Just encountered the same problem. @pablorsk workaround works, but the solution also references a version by a commit hash. I think it's still a bad idea and is just as prone to break again as it was before. Why not use a labelled version ?
This is being broken by npm v5. Falling back to npm v3 the hash still works as expected
@Protectator is not released yet on https://www.npmjs.com/package/gulp
But, this can be fixed running:
npm install --save-dev gulpjs/gulp#4.0
Description
Gulp package is broken
Error Message & Stack Trace
Config