Closed UnspeakableHorror closed 8 years ago
These CIs are being useless lately, npm thing not downloading something because the network was busy or whatever, Solano sometimes can't find the mount point for the code, templates go missing even though I changed nothing related to that, stuff failing because the CI doesn't support embedded Redis (wtf?) and so on.
The best part is that right after pushing this the first thing I thought was "let's see what fails now..." and of course something failed.
From CircleCI, I guess the same is happening on Solano.
Error: The libsass
binding was not found in /home/ubuntu/vyllage/assets/node_modules/gulp-sass/node_modules/node-sass/vendor/linux-x64-11/binding.node
This usually happens because your node version has changed.
Run npm rebuild node-sass
to build the binding for your current node version.
at Object.sass.getBinaryPath (/home/ubuntu/vyllage/assets/node_modules/gulp-sass/node_modules/node-sass/lib/extensions.js:158:11)
at Object.
npm ERR! Linux 3.14.28-031428-generic
npm ERR! argv "node" "/home/ubuntu/nvm/v0.10.33/bin/npm" "run" "build"
npm ERR! node v0.10.33
npm ERR! npm v2.13.5
npm ERR! code ELIFECYCLE
npm ERR! project-assets@0.0.0 build: gulp build
npm ERR! Exit status 8
npm ERR!
npm ERR! Failed at the project-assets@0.0.0 build script 'gulp build'.
npm ERR! This is most likely a problem with the project-assets package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! gulp build
npm ERR! You can get their info via:
npm ERR! npm owner ls project-assets
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request: npm ERR! /home/ubuntu/vyllage/assets/npm-debug.log
@tylerbenson Is there any chance of using fixed versions for dependencies in the frontend? So it does not decide to update and break everything every other day?
Forgot to add doc.
Closes https://github.com/natebenson/vyllage/pull/1191.