Help getting "sh: 1: concurrently: not found" error

Hello this is like my first deploy of this type and running into issues with this. I was having a “sh:1:vite build” changed a EVN on render and it moved on to give a link issue for the css file for the page. I commented it out still will need to figure that out but i wanted to get the page to display at least. Can someone help out this noob. Thanks here is what error log i have

INFO✓ built in 4.19s

Jun 9 01:02:16 PMINFO==> Uploading build…

Jun 9 01:02:27 PMINFO==> Build uploaded in 9s

Jun 9 01:02:27 PMINFO==> Build successful :tada:

Jun 9 01:02:31 PMINFO==> Deploying…

Jun 9 01:03:17 PMINFO==> Using Node version 20.12.2 (default)

Jun 9 01:03:17 PMINFO==> Docs on specifying a Node version: Setting Your Node.js Version | Render Docs

Jun 9 01:03:17 PMINFO==> Using Bun version 1.1.0 (default)

Jun 9 01:03:17 PMINFO==> Docs on specifying a bun version: Setting your Bun Version | Render Docs

Jun 9 01:03:21 PMINFO==> Running ‘npm run web’

Jun 9 01:03:23 PMINFO

Jun 9 01:03:23 PMINFO> lb-dungen@1.0.0 web

Jun 9 01:03:23 PMINFO> concurrently “cd server && npm run start” “cd client && npm run dev”

Jun 9 01:03:23 PMINFO

Jun 9 01:03:23 PMINFOsh: 1: concurrently: not found

Jun 9 01:03:24 PMINFO==> Common ways to troubleshoot your deploy: Troubleshooting Your Deploy | Render Docs

Jun 9 01:03:24 PMINFO==> Using Node version 20.12.2 (default)

Jun 9 01:03:24 PMINFO==> Docs on specifying a Node version: Setting Your Node.js Version | Render Docs

Jun 9 01:03:24 PMINFO==> Using Bun version 1.1.0 (default)

Jun 9 01:03:24 PMINFO==> Docs on specifying a bun version: Setting your Bun Version | Render Docs

Jun 9 01:03:29 PMINFO==> Running ‘npm run web’

Jun 9 01:03:35 PMINFO

Jun 9 01:03:35 PMINFO> lb-dungen@1.0.0 web

Jun 9 01:03:35 PMINFO> concurrently “cd server && npm run start” “cd client && npm run dev”

Jun 9 01:03:35 PMINFO

Jun 9 01:03:35 PMINFOsh: 1: concurrently: not found

link to github GitHub - Fitbert/LB-Dungen: The final project

So small update, I got a work around for this issue i created a start.js file with this code following and then updated the json to run the start.js file.
It has worked to get around the concurrently for now but i would like to know how to correctly fix this issue please.

const { spawn } = require(‘child_process’);

const server = spawn(‘npm’, [‘run’, ‘start’], { cwd: ‘server’, stdio: ‘inherit’ });
const client = spawn(‘npm’, [‘run’, ‘dev’], { cwd: ‘client’, stdio: ‘inherit’ });

server.on(‘close’, (code) => {
console.log(Server process exited with code ${code});
client.kill();
});

client.on(‘close’, (code) => {
console.log(Client process exited with code ${code});
server.kill();
});

Hi there,

Can you please elaborate on what your current question is? I’m afraid I’m not following.

Regards,
Mike


Render Support Engineer, MT (UTC-6, UTC-7 in Winter)