The failure is Error: ENOENT: no such file or directory, scandir '.../node_modules/node-sass/vendor. Downgrading to version 4.5.2 resolves the issue.
Cannot reproduce locally and as it's a managed environment I can only extract some of the version information from the build log:
$ node --version
v6.10.3
$ npm --version
3.10.10
$ nvm --version
0.33.2
Travis configuration:
https://github.com/miguelcobain/ember-paper/blob/cef52e7638615e44249775b0663ba8f48d7bb8c1/.travis.yml
Failing job:
https://travis-ci.org/miguelcobain/ember-paper/jobs/233735922
Successful job:
https://travis-ci.org/miguelcobain/ember-paper/jobs/233735922
The only difference is the node-sass version.
The only think 4.5.3 added as support for another module version of Node 8 https://github.com/sass/node-sass/compare/v4.5.2...v4.5.3
This looks like another general yarn caching issue https://github.com/sass/node-sass/issues/1804
Sounds like a reasonable explanation but using --force or removing Yarn cache usage in .travis.yml does not appear to help.
Please file an issue with yarn. They're actively trying to address
node-sass incompatibilities
On 18 May 2017 10:13 pm, "Björn Harrtell" notifications@github.com wrote:
Sounds like a reasonable explanation but using --force or removing Yarn
cache usage in .travis.yml does not appear to help.—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/sass/node-sass/issues/1971#issuecomment-302528183,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAjZWO3g-nPKolJ0FEI-thrc-VFdeU4pks5r7KZqgaJpZM4Nfr1h
.
Confirmed to be more or less the same issue as described in https://github.com/yarnpkg/yarn/issues/1981. The workaround npm rebuild node-sass run as the postinstall script works in my case too. Sorry for the noise.
Had the same issue but instead of adding it inside the package.json a put the following code in the .travis.yml
before_script: npm rebuild node-sass;
Works great for me.
Most helpful comment
Confirmed to be more or less the same issue as described in https://github.com/yarnpkg/yarn/issues/1981. The workaround
npm rebuild node-sassrun as thepostinstallscript works in my case too. Sorry for the noise.