gulp-header update bug

[benjamincanac]

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.

[benjamincanac]

#125

[bbuhler]

Seems to be caused by this commit gulp-community/gulp-header@7feb211.

[philjones88]

Same issue here. Resorted to npm shrinkwrap and defining version 1.8.2 of this package.

[doofer]

So an alternative solution, until this is accepted, is to include the
"gulp-header": "1.8.2", in package.json

[bondarewicz]

are you guys getting something along those lines? :

fs.js:839
[return binding.lstat(pathModule._makeLong(path));
Error: ENOENT: no such file or directory, lstat 'C:\...\eb5dfb8f3a5dbb94\src\app\templateCacheHtml.js'

[curvedental]

We worked around the issue by installing gulp-header@1.8.2 as well

[grtjn]

Observing it too: marklogic-community/slush-marklogic-node#365

[grtjn]

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..

[warlyware]

This is the error I was getting all morning:

fs.js:0
(function (exports, require, module, __filename, __dirname) { // Copyright Joy

Error: ENOENT, no such file or directory '/var/www/src/templates.js'

and "gulp-header" was the culprit. Adding "gulp-header": "1.8.2" to package.json fixed it. Thanks all!

[gamebox]

@warlyware This worked by adding to your own application's package.json?

[mikejr83]

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.

[SamMorrowDrums]

Considering npm shrinkwrap myself now! Not the first time I've been bitten by things like that!

[grtjn]

That worked for us, just put gulp-header above gulp-angular-templatecache, npm uninstall gulp-angular-templatecache, and do npm install..

[vinicius33]

Same problem here. Adding "gulp-header": "1.8.2" to package.json worked for me.

[clocked0ne]

Why do they do this on a Friday afternoon??? >:( 👎

[DinisCruz]

yes that also worked for me

what was the root cause of the problem?

[alejandrolechuga]

gulp-header: 1.8.2 worked

[grtjn]

Root cause is in gulp-header, see also gulp-community/gulp-header#37

[andrewcurtis-mris]

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

[nkanand4]

There are more like this, just waiting for others to break when the deps change.
"gulp-footer": "1.x", "gulp-concat": "2.x"

[spg]

gulp-header: 1.8.2 worked for me too, thx for reporting this problem. This saved my team a lot of time.

[candyam5522]

gulp-header: 1.8.2 worked for me

[Schwankenson]

gulp-header: 1.8.2 worked for me too, thx for reporting this problem. This saved my team a lot of time.

[evankleist]

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

[SamMorrowDrums]

Haha, I spent too long on it too. I set up CI server to run with Upstart,
then had issues with npm and no $HOME environmental variable, and then hit
this!

Initially I just assumed any issues were my fault...

On Fri, 17 Jun 2016, 23:19 evankleist, notifications@github.com wrote:

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

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#124 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AElqXmWvBpHQJfFAkERl4t9H6UD35VHNks5qMx1agaJpZM4I4M_Q
.

[sandy724]

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.

[mydata]

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.

[SamMorrowDrums]

The appropriate way to debug this is really:

• Read the stack trace (the fs command showed the library call in which it
  broke)
• look at the code on the mentioned line
• double check your calling code, just in case something has changed
• check npm for version changes (going back through the stack trace if
  required)
• Revert dep if required

The problem is, we developers often work from the assumption that if you
encounter an error, it is always in your code, while the reality is
libraries can be at fault.

Some advice:

• believe stack traces, the library code call stack, can be the source of
  the error.
• take a deep breath when debugging streams, particularly when you only
  wrote the plumbing code, and all the streaming is in third party libraries,
  the async stack traces can be really poor, but they almost always hint at
  the answer.

The systemic problem, is that npm allows packages to be published with
loose semver for their deps. Personally, while it takes burden off
publishers, it does so at the cost of reliability. Shrinkwrap is a good
call for production apps or at least strict dependencies in your
package.json, which would let you eliminate first layer of dependencies
having changed.

On Sat, 18 Jun 2016, 05:17 mydata, notifications@github.com wrote:

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.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#124 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AElqXjJOlC18rWbgeMKsX5T2eT7nqHEBks5qM3FYgaJpZM4I4M_Q
.

[cfrezier]

Putting gulp-header: 1.8.2 above gulp-angular-templatecache worked for me

[ghost]

🙀
But, gulp-header: 1.8.2 works

[miickel]

A fix is on the way to NPM now. 🚀 Thanks for brining this to my attention!

[tabladrum]

still breaking. Is it there yet?

[miickel]

@tabladrum make sure you have 1.9.0 installed

cat node_modules/gulp-angular-templatecache/package.json | grep version

[tabladrum]

👍 Thanks!

[Soumya-mp]

This is still breaking....