-
Notifications
You must be signed in to change notification settings - Fork 103
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
gulp-header update bug #124
Comments
Seems to be caused by this commit gulp-community/gulp-header@7feb211. |
Same issue here. Resorted to |
So an alternative solution, until this is accepted, is to include the |
are you guys getting something along those lines? :
|
We worked around the issue by installing gulp-header@1.8.2 as well |
Observing it too: marklogic-community/slush-marklogic-node#365 |
Creating an empty file in the spot gulp-header is looking also works as work-around, but I like reverting to 1.8.2 better.. |
This is the error I was getting all morning:
and |
@warlyware This worked by adding to your own application's package.json? |
We've been bitten by this issue as well. Can confirm that adding gulp-header@1.8.2 to our package.json short-circuits node into using that version for the dependency resolution. |
Considering npm shrinkwrap myself now! Not the first time I've been bitten by things like that! |
That worked for us, just put gulp-header above gulp-angular-templatecache, npm uninstall gulp-angular-templatecache, and do npm install.. |
Same problem here. Adding "gulp-header": "1.8.2" to package.json worked for me. |
Why do they do this on a Friday afternoon??? >:( 👎 |
gulp-header: 1.8.2 worked |
Root cause is in gulp-header, see also gulp-community/gulp-header#37 |
I would propose that the true deficiency here are the loose dependency definitions. With all of this project's dependencies defined as 1.x or 2.x etc this project will be subject to pulling in any defects introduced in any of its downstream dependencies at any time. This one just happened to be in gulp-headers 1.8.3 |
There are more like this, just waiting for others to break when the deps change. |
gulp-header: 1.8.2 worked for me too, thx for reporting this problem. This saved my team a lot of time. |
gulp-header: 1.8.2 worked for me |
gulp-header: 1.8.2 worked for me too, thx for reporting this problem. This saved my team a lot of time. |
Well I spent my whole day trying to fix this, thinking it was a problem with my gulp tasks. At least I finally found this thread |
Haha, I spent too long on it too. I set up CI server to run with Upstart, Initially I just assumed any issues were my fault... On Fri, 17 Jun 2016, 23:19 evankleist, notifications@github.com wrote:
|
Is there a better way to figure out these kinds of issue, what is the approach to debug such issues. I luckily stumbled on this thread otherwise I didn't had any direction where to look. |
Even i was also spent almost whole day thinking it was due to other reasons like folder permission, node server issues , gup issues etc. At last found this thread and applied the temporary fix and got the build working. |
The appropriate way to debug this is really:
The problem is, we developers often work from the assumption that if you Some advice:
The systemic problem, is that npm allows packages to be published with On Sat, 18 Jun 2016, 05:17 mydata, notifications@github.com wrote:
|
Putting gulp-header: 1.8.2 above gulp-angular-templatecache worked for me |
🙀 |
A fix is on the way to NPM now. 🚀 Thanks for brining this to my attention! |
still breaking. Is it there yet? |
@tabladrum make sure you have 1.9.0 installed
|
👍 Thanks! |
This is still breaking.... |
Hi,
An hour ago the gulp-header module has been updated to v1.8.3 but it broke templatecache.
Can you fix the version ?
Thanks.
The text was updated successfully, but these errors were encountered: