node-sass: EINVAL: invalid argument, open '/code/node_modules/node-sass/package.json'

I’m aware this issue has been closed, but it’s still a problem for me.

It appears that this has been closed under the premise that this is a problem with npm, node, docker, windows, or some other utility. Have issue(s) been filed in the appropriate repositories so that I can track them? Can we reference those issues so others, like me, that stumble here can find the appropriate issues?

In fact, @gwenl, the accepted answer here is what is now working for me: https://stackoverflow.com/questions/29181032/add-a-volume-to-docker-but-exclude-a-sub-folder

It seems for me that the synchronization between my Windows host and Linux container was mixing a lot up.

If you want to have subdirectories ignored by docker-compose but persistent, you can do the following in docker-compose.yml:

volumes:
  node_modules:
services:
  server:
    volumes:
      - .:/app
      - node_modules:/app/node_modules

This will mount your current directory as a shared volume, but mount a persistent docker volume in place of your local node_modules directory. This is similar to the answer by kernix, but this will allow node_modules to persist between docker-compose up runs, which is likely the desired behavior.

Hello,

I have a Windows 10 with docker and I use the following workaround. Into the docker, in my home I create a directory, for example <project name>/node_modules. Them in my mapped directory within windows and linux(into the docker) I make a symbolic link within the directory I created before an “node_modules”. Something like ln -s <src> <dest> ln -s /home/my_project/node_modules /var/www/html/my_project/node_modules

Them, into my project I call the npm install

With this solution, the node-sass install with no problem.

I’m not an expert but I think the problem was the mapping within the windows and linux and the way that npm installs with links this package.

Best regards

I have the same error in the same environment (@METACEO : I guess you run docker on Windows ?), and indeed it seems to be related to how the directories in the container are mapped on the host. Maybe some magic with symlinks that the host FS doesn’t understand ? If I move package.json to another directory within the container that is not mapped on the host (say /tmp/), the npm install just goes fine.

It used to work quite recently so I guess some dependency changed its behavior in the meantime.

It seems there is no such problem with yarn, so I’ll temporarily switch away from npm.

I have exactly the same issue that I can reproduce as follow:

Context

Windows 10, WSL

$ uname -a
Linux nowox-pc 4.4.0-17134-Microsoft #471-Microsoft Fri Dec 07 20:04:00 PST 2018 
x86_64 x86_64 x86_64 GNU/Linux

$ docker --version
Docker version 18.09.1-beta1, build d3184b7

Minimal project

Only one package.json

$ tree
.
+-- package.json

0 directories, 1 file

$ cat package.json
{
  "devDependencies": {
    "node-sass": "^4.9.2"
  }
}

Failure on npm install

$ docker run -itv $(pwd -P):/app -w=/app node npm install

> node-sass@4.11.0 install /app/node_modules/node-sass
> node scripts/install.js

fs.js:121
    throw err;
    ^

Error: EINVAL: invalid argument, open '/app/node_modules/node-sass/package.json'
    at Object.openSync (fs.js:450:3)
    at Object.readFileSync (fs.js:350:35)
    at Object.Module._extensions..json (internal/modules/cjs/loader.js:738:20)
    at Module.load (internal/modules/cjs/loader.js:620:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:560:12)
    at Function.Module._load (internal/modules/cjs/loader.js:552:3)
    at Module.require (internal/modules/cjs/loader.js:657:17)
    at require (internal/modules/cjs/helpers.js:22:18)
    at Object.<anonymous> (/app/node_modules/node-sass/lib/extensions.js:7:9)
    at Module._compile (internal/modules/cjs/loader.js:721:30)

I have added a .npmrc with rollback=false and I can confirm that package.json is readable:

$ docker run -itv $(pwd -P):/app -w=/app node head -n2 /app/node_modules/node-sass/package.json
{
  "_from": "node-sass@^4.9.2",

I had the extact issue yesterday. I have a windows 10 environment with docker running. I created an SPFX project using yeoman and after the scaffolding it gave out the same error.

I run the command yarn and it all went well.