Instead of the default "start": "react-scripts start" specified in your package.json file, try changing it to the following and then try: "scripts": { "start": "node ./node_modules/react-scripts/bin/react-scripts.js start" }

Solution 1:

I think you have react-script globally installed. so try this command

npm install react-scripts --save

and then run the application again.

Solution 2:

try this command

sudo chmod +x node_modules/.bin/react-scripts

and then run the application again.

Solution 3;

I think your npm not have permission. you can try to run by sudo

sudo npm run build

and you can fix this problem like this

Step 1:

check path of npm if you are using npm by

which npm

you will "/usr/local/bin/npm" this type of path

OR

check path of yarn if you are using yarn by

which yarn

you will "/usr/local/bin/npm" this type of path

Step 2:

give permission 777 to this path and try to run project

sudo chmod -R 777 /usr/local/bin/npm

It seems you don't have the right permission to build or execute the react app,

What you could do is try changing the owner to the current user using

   sudo chown -R username:username /var/lib/jenkins/workspace/MedAverter/medaverter-front/

you can check your username by typing whoami in the terminal this is done because the current user does not have access to to the var folder or anything inside it by default. Furthermore you want to change the access mode to read and execute for everyone using

 sudo chmod 755 /var/lib/jenkins/workspace/MedAverter/medaverter-front/

then you can want to change to root user using

sudo su

and then build the app using

npm run build

This has worked for me when i was facing somewhat a similar problem , hopefully it works for you as well,Cheers :)

I finally figured out a solution to this problem. It took days of effort. First, I deleted the Jenkins project and created a new one using Pipeline, rather than Freestyle. Then I added a Jenkinsfile with a script. That continued to fail but now I had the flexibility to add in additional commands to handle the errors.

One new error was something about jest-worker. I ran the following command on the DigitalOcean server to get past that one:

yarn add jest-worker

Then I had the old permissions error again. I think all these permission errors are due to user jenkins trying to run things owned by user root, even though everything had 777 permissions. I don't understand that but here's how I got around it. Modify the /etc/sudoers file and add the following line:

jenkins ALL=(ALL) NOPASSWD:ALL

Then modify the Jenkins file script to include recursive chmod and chown. Here is the full script that FINALLY worked:

pipeline {
    agent any
    stages {
        stage('Checkout') {
            steps {
                echo 'Checkout...'
                sh 'sudo chmod -R 777 /var/lib/jenkins/workspace/MedAverter/medaverter-front'
                checkout scm
                sh 'sudo chmod -R 777 /var/lib/jenkins/workspace/MedAverter/medaverter-front'
                sh 'sudo chown -R jenkins /var/lib/jenkins/workspace/MedAverter/medaverter-front'
                stash 'sources'
            }
        }
        stage('Build') {
            steps {
                echo 'Build...'
                unstash 'sources'
                sh 'sudo chmod -R 777 /var/lib/jenkins/workspace/MedAverter/medaverter-front'
                sh 'sudo chown -R jenkins /var/lib/jenkins/workspace/MedAverter/medaverter-front'
                sh 'mvn clean package -DskipTests'
                stash 'sources'
            }
        }
    }
}

I also had to increase the memory of the DigitalOcean droplet from 1GB to 2GB to get past another error. If someone knows a better way to get past that frustrating permissions error, please comment.

From the root of your project run:

chmod +x node_modules/.bin/react-scripts

I had modified the permissions on the folders earlier and undid the changes. I believe that is it.

I just deleted the node_modules folder and reinstalled the dependencies with the yarn command.

sudo rm -rf node_modules
yarn
yarn start

That happens because of lack of a package.json file Just run this command and the issue will be fixed:

npm audit fix

Sometimes npm need root permission. Try using sudo in the command. It resolved a similar issue for me. This might help.

sudo npm run build