search

vigetlabs / gulp-rails-pipeline

Ditch the Rails Asset Pipeline and roll your own with Gulp
MIT License
646 stars 64 forks source link

npm install fails #18

Open phulst opened 9 years ago

phulst commented 9 years ago

I cannot get 'npm install' to succeed in this project. I keep getting the following error: 

> gulp-rails@ postinstall /Users/peter/projects/lifesizey/gulp-rails-pipeline
> gulp build

util.js:634
  ctor.prototype = Object.create(superCtor.prototype, {
                                          ^
TypeError: Cannot read property 'prototype' of undefined
    at Object.exports.inherits (util.js:634:43)
    at Object.<anonymous> (/Users/peter/projects/lifesizey/gulp-rails-pipeline/node_modules/browser-sync/node_modules/http-proxy/lib/http-proxy/index.js:108:17)
    at Module._compile (module.js:460:26)
    at Object.Module._extensions..js (module.js:478:10)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Module.require (module.js:365:17)
    at require (module.js:384:17)
    at Object.<anonymous> (/Users/peter/projects/lifesizey/gulp-rails-pipeline/node_modules/browser-sync/node_modules/http-proxy/lib/http-proxy.js:4:17)
    at Module._compile (module.js:460:26)

npm ERR! Darwin 14.3.0
npm ERR! argv "/Users/peter/.nvm/v0.12.2/bin/node" "/Users/peter/.nvm/v0.12.2/bin/npm" "install"
npm ERR! node v0.12.2
npm ERR! npm  v2.7.4
npm ERR! code ELIFECYCLE
npm ERR! gulp-rails@ postinstall: `gulp build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the gulp-rails@ postinstall script 'gulp build'.
npm ERR! This is most likely a problem with the gulp-rails package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     gulp build

I have tried with various versions of node 0.10, 0.11 and 0.12 but always get the same error. Any suggestions on how to resolve this? Googling around got me nowhere... thanks

phulst commented 9 years ago

updating the following dependency in package.json

"browser-sync": "~1.9"

resolved the issue for me.

joeswann commented 9 years ago

Can confirm this also works with: "browser-sync": "~2.4.0",

raebot commented 9 years ago

Had the same issue, got it to work with "browser-sync": "~2.4.0". Thanks, @phulst @joeswann .