9

The following error will be displayed when i use the command "npm start".

> [email protected] start /var/www/html/dev/callcenter
> react-scripts start

sh: 1: react-scripts: Permission denied

npm ERR! Linux 4.4.0-1013-aws
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "start"
npm ERR! node v6.10.0
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE
npm ERR! [email protected] start: `react-scripts start`
npm ERR! Exit status 126
npm ERR!
npm ERR! Failed at the [email protected] start script 'react-scripts start'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the callcenter package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     react-scripts start
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs callcenter
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls callcenter
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /var/www/html/dev/callcenter/npm-debug.log
1
  • The user callcenter (which executes the script) probably has no access to the path required (/var/www/html). Check permissions on this folder. To validate this is the issue, try to execute this script as root (if possible).
    – Chen A.
    Commented Jul 26, 2017 at 13:30

4 Answers 4

14

Make sure that your react-script binary is executable.

$ chmod +x node_modules/.bin/react-scripts
0
9

I encountered the same issue, Surprisingly it works fine in Windows but failed in Linux giving the same error. Follow below step to resolve this issue.

you need to change package.json file inside your project folder like below instead of default value of "start": "react-scripts start"

"scripts": { "start": "node ./node_modules/react-scripts/bin/react-scripts.js start" }

0
7

Although the OP doesn't really refer to my problem, this was the first stackexchange result in Google when searching for yarn build webpack: Permission denied, hence I'm adding my solution here in case it helps someone.

For those landing here because they are finding webpack: Permission denied when running yarn build on Linux even though the command works fine on Windows:

The problem in my case was that the *.lock files had some relation with the environment in which they were generated (Windows) and wouldn't work in a different environment (WSL2 - Ubuntu)

  1. Remove node_modules

    rm -vrf node_modules
    
  2. Remove locks

    rm package-lock.json
    rm yarn.lock
    
  3. Run yarn

    yarn
    yarn build
    
0

Delete your node_modules folder and install it again with npm install.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .