Just to update from my end. I found that for some reason no matter what I did even after the permissions issue was resolved, it still wouldn’t always run the install.js script. I also noticed it tends to happen when its only part of a large set of downloads.

As a safe guard, I just started running the install.js file after NPM Install command part of my build. This ensured that the vendor folder was always present.

Can’t explain why the install file doesn’t always get ran on each build. So my build script looks like this:

npm update npm install nodejs node_modules/node-sass/scripts/install.js npm rebuild node-sass

npm will only execute install scripts for direct dependencies in your package.json. This is a performance optimisation on their end which is unfortunate.

npm rebuild node-sass is the official solution. Deleting your node_modules and running npm install will also do the trick.

This commonly happens in CI systems because they’ll typically run npm install with the default OS Node. Later in their script they’ll switch a new version of Node. Native extension are compiled against the version of Node that npm was using during install. This means the new Node cannot see the extension built during install.

In this case, running npm install again doesn’t fix the issue because npm thinks it is installed. This is why you must run npm rebuild node-sass.

@peterpme I was able to fix this on heroku by turning off NODE_MODULES_CACHE

heroku config:set NODE_MODULES_CACHE=false

npm rebuild node-sass

I have same problem, run npm rebuild node-sass resolve it.

npm rebuild node-sass fixed the issue for me.

The vendor directory is created during npm install. Try deleting your node_modules and running npm install. On 22 Jun 2016 2:02 AM, “dustin-page” notifications@github.com wrote:

Note your Gulp-Sass installation referenced above is installing: node-sass@3.7.0

But when you do it manually you are installing: node-sass@3.4.2

Version 3.4.2 doesn’t have “vendor” in the “files” array I referred to in previous comment, but version 3.7.0 does.

package.json version 3.4.2: “files”: [ “bin”, “binding.gyp”, “lib”, “scripts”, “src” ],

package.json version 3.7.0: “files”: [ “bin”, “binding.gyp”, “lib”, “scripts”, “src”, “vendor” ],

— 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/1579#issuecomment-227487362, or mute the thread https://github.com/notifications/unsubscribe/AAjZWIJUYcMtWAKcDWs5fXNLpdHbggo7ks5qOArvgaJpZM4Ivk6Q .

Hi everybody,

When deploying to Heroku, I continue to have this issue even after running npm rebuild node-sass. Does anybody else feel the same way?

It appears that there was a permissions issue running install.js.

I’m not sure why it was doing it intermittently, but I simply changed the access rights to the build folder.

NPM seems to not give you a notification if install.js fails to run correctly.

I had this issue trying to deploy to Heroku after I started to import some css inside JS packs with Webpacker which uses Yarn. npm rebuild node-sass did help, and one way to make it work during Heroku deployment is to put this to package.json:

  "scripts": {
    "postinstall": "npm rebuild node-sass"
  }

npm rebuild node-sass

I have same problem, run npm rebuild node-sass resolve it.

I have the same problem, and after: sudo npm rebuild node-sass It was the solution to the problem…

We’ve just started having this issue intermittently on our build servers using Yarn 0.18.1. Our build was previously stable; we’re having a hard time figuring out what’s changed. Just posting here in case anyone else is also suddenly encountering this issue too.

Update: Our problem seems to be https://github.com/yarnpkg/yarn/issues/1832

@mrking

nodejs node_modules/node-sass/scripts/install.js npm rebuild node-sass

I ran this for every package that gave ENOENT and now everything if working. thanks alot!

for some reason the install script wasn’t invoked when i ran npm install

Use npm install node-sass or Linux npm install node-sass --no-bin-links

This problem was happening on a build server where the folder was clean on each build. So your suggestion of deleting the node_modules folder didn’t fix the issue in my case as there wasn’t a node_modules folder to begin with.

I don’t know enough about how NPM works to comment on your bit of information. If you want me to do any additional logging, I can still reproduce the problem fairly consistently. However, I have my work around for now 👍

However, seeing no one else has reported this until now, whatever it is, its not widespread. Probably not good utilization of time.

npm rebuild node-sass resolved it for me too.

Every 19 out of 20 deployments on heroku for my apps that use this package simply crash due to this problem 😃 I keep pushing the same commit until Heroku builds it. That seems to be the only solution right now, yes? Rebuild until it works?

Vagrant box can use: npm rebuild node-sass --no-bin-links Thank for this topic.

Simlar problem with node-sass v3.7.0. I get the following error: Error: ENOENT: no such file or directory, scandir ‘C:\Working\my-app\node-sass\vendor’

In the package.json file it is looking for the “vendor” directory, which doesn’t exist:

“files”: [ “bin”, “binding.gyp”, “lib”, “scripts”, “src”, “vendor” ],

Rolling back “node-sass” to “3.4.0” temporarily fixed the issue for me. However, I am now locked into this version.

Same issue suddenly appeared magically in Dockerfile builds. Downgraded npm 6.6 to 6.5 and then it worked again.

The workaround fix by @devmedios worked for our Docker CI pipeline. 😅 npm i node-sass --no-bin-links Thanks!

This problem started appearing after rebuilding our docker image today (no change to Dockerfile content), reverting back to old docker image works.

the docker file looks like this:

FROM node:8.9-slim

RUN apt-get update && \
  apt-get install -y --no-install-recommends git mysql-client openssh-client \
          python \
          libcairo2-dev libjpeg-dev libpango1.0-dev libgif-dev build-essential g++ \
          libpng-dev && \
  npm i -g yarn lerna && \
  rm -rf /var/lib/apt/lists/*

so the problem is one of the following:

• node / npm
• yarn
• lerna
• other OS packages

The weird thing is, even after fixing the version of yarn and lerna, the problem still exists:

npm i -g yarn@1.12.3 lerna@3.4.3 && \

node-sass & bug

Module build failed: Error: ENOENT: no such file or directory, scandir 'node_modules\node-sass\vendor'

solution

delete node_modules folder & re-install all modules

OR

delete package.json "node-sass": "^4.7.2", & re-install npm i -D node-sass@4.7.2

OK

I had the same issue. My installed version for node-sass was 3.1.0. I upgraded it to 3.7.0 which contains vendor files and now it is working fine.

Deleting node_modules/node-sass and reinstalling didn’t seem to work for me. @ERPedersen’s solution worked.

I ran into this problem with node 8.5.0 and node-sass 4.5.3. Fixed it by deleting the node_modules/node-sass directory and reinstalling.

But exactly what is the cause of the problem?

Thank you @mrking, simply npm rebuild node-sass did the trick here (MacOS)

@pencilcheck - I was running into the same issue. Add

npm rebuild node-sass &&

Before your build/start script for heroku and it’ll recompile node sass before building your app packages.

The only thing I had to do on TravisCi was:

script:
- npm rebuild node-sass
- npm run build

After that it worked, thanks

npm rebuild works sometimes. The only thing that always works for me to get rid of this ridiculous annoying bug is to just go npm install node-sass@random-compatible-different-version

Had the same problem. After running

npm update

Everything worked fine