Inquiry: Is `--no-same-owner` the possible cause for issues such as `cannot run in wd`

[joshlangner]

While researching the issue discovered when trying to run install scripts in package.json, where I receive error cannot run in wd (Example: https://stackoverflow.com/questions/18136746/npm-install-failed-with-cannot-run-in-wd), I suspected permission or ownership discrepancies, and traced down to where nodejs was actually being installed and by what user.

Is it possible that the inclusion of --no-same-owner can cause install scripts to fail?

https://github.com/nodejs/docker-node/blob/fdd2b251827817ac7bb4f0b2b082483abff8ea77/12/stretch/Dockerfile#L39

Many recommendations are to run npm with the flag --unsafe-perm or other risky actions, which, obviously, is not safe. I'd love to identify the root issue and resolve it, if possible.

[matrix4123]

@joshlangner Were you able to resolve this? I am getting a similar error but within postinstall.

"cd ./functions && npm install --unsafe-perm && cd ../plugins/firestore-local && npm install --unsafe-perm"

I am trying to run this command and getting the 'cannot run in wd' error.