EINVAL Spawning error when getting Quickstart-react app

Hello there @dansan1984 and welcome to the community!

I found a few links of discussions about this that might be useful for you:

Hi,

Thanks for your reply. Unfortunately all these issues seems to get solved by the software vendor using NodeJS.

Both SAP and Node-RED have released a patch to fix this issue. Could it be that Monday needs to release a new version of the quickstart-react top fix this?

Hello again,

We do not see any reports of other users having this issue, but if youfill this form (https://support.monday.com/hc/en-us/requests/new?ticket_form_id=13855862562962) adding as much information as possible to it (such as account ID, board IDs, item IDs, timestamps, etc.) we can check with our team!

Cheers,
Matias

I’m having the same problem and I can’t find a solution that solves it

Hello there @Fabiogut,

Would you be able to please fill the same form (https://support.monday.com/hc/en-us/requests/new?ticket_form_id=13855862562962) so that our team can take a look into it?

Same problem - I will fill out the form.

Hello there!

Thank you for filling the form! We will check this with our team 😀

Hi Sorry for the ate reply, I’ve filled out the form

Hello everyone here!

General question. Are you using Windows? If so, are you using Node 18.x?

Using windows ( windows 11 ) and Node.js v20.12.2.

Hello again,

Matias here!

May I ask from all of you to please send over the ID of your tickets? We are investigating this.

My ticket number is: 3438560

This seems to be a general problem with a new node.js security update. There is a way a way to get around it. In my

C:\\Users[username]\\AppData\\Local\\npm-cache_npx\\d810257f6f2ee4ed\\node_modules\\node-run-cmd\\index.js

I amended line 42 to read

const spawnProcessOpts = {shell:true};

That should allow your shell to spawn another .cmd process and fix your issue.