EINVAL Spawning error when getting Quickstart-react app

monday Apps & Developers
, , ,
1

Hi fellow devs,

Trying to get my dev environment up and running on a windows machine, but running into an error with the CLI

image
image836×320 9.09 KB

This error has been described here and requires an addition of { shell: true } when Spawning objects. However I’m unsure if this addition needs to be made in the NPX application or in the “Quickstart-react” code.

Did anyone run into this or a similar issue?

Kr,

Daniel

2

Hello there @dansan1984 and welcome to the community!

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

3

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?

5

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

6

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

image
image1094×461 24.5 KB

7

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?

8

Same problem - I will fill out the form.

image
image1920×1080 268 KB

10

Hello there!

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

11

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

12

Hello everyone here!

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

13

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

14

Hello again,

Matias here!

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

15

My ticket number is: 3438560

16

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.