not working with Node.js version 20.12.x

Question

not working with Node.js version 20.12.x

kireerik opened this issue 7 months ago · 12 comments

ELIFECYCLE Command failed with exit code 3221226505.

With Node.js version 20.11.x it is working.

Versions: Windows (10)
nodemon -v: 3.1.0
Operating system/terminal environment (powershell, gitshell, etc): cmd
Using Docker? What image: No.
Command you ran: nodemon

closes getsentry/sentry-javascript#11453

remy commented 7 months ago

Also no.

Answer 1 · 2024-04-18T13:01:20.000Z

Does not error as per the detail given in the original issue.

Will close shortly unless there's any additional (or any ) details.

Answer 2 · 2024-04-18T13:03:16.000Z

Actually will close and reopen later if any details are offered. This doesn't read like a nodemon issue (but…again, very little info).

Answer 3 · 2024-04-19T10:50:27.000Z

With 20.11.x it works (just like it does for you in your comment above).

With 20.12.x it is not working.

Answer 4 · 2024-04-19T14:56:46.000Z

It is according to the directions you offered.

Answer 5 · 2024-04-22T10:11:12.000Z

Seems like this issue occurs (with Node.js version 20.12.x) when the --env-file option is used (example --env-file .env).

Answer 6 · 2024-04-29T08:14:21.000Z

Did you use version 20.12.x?

We have a setup like this:
start script in packages/package/package.json:

nodemon --env-file=.env src/index.mjs

.env file is in packages/package
nodemon is installed for the package workspace

command to reproduce the issue: pnpm --filter package start

Removing --env-file=.env from the start script makes it start properly with Node.js version 20.12.x as well.

Answer 7 · 2024-04-29T13:31:45.000Z

You can see I used node 20 from my previous screenshot.

Provide a pared down repo to replicate the issue then I can look at this properly because so far you've drip fed me information on what you're seeing and it's not helpful (ie. now adding that you're using pnpm is another variable).

Answer 8 · 2024-04-29T14:50:43.000Z

The issue happens with Node.js version 20.12.x.

Answer 9 · 2024-04-29T15:32:19.000Z

No, it doesn't: #2194 (comment)

It's happening on your machine and you've not provided details to replicate.

Last time I ask for details to replicate.

Answer 10 · 2024-05-03T17:40:30.000Z

Seems like I was able to reproduce it. It looks like it happens when the .env file contains a variable that is at least 292 characters long and when the value is provided in (double or single) quotes.
Example:

test="abcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabcabca"

Not using quotes at all works as expected.

Answer 11 · 2024-05-03T18:30:31.000Z

Locking this issue to avoid confusing anyone. I've repeatedly asked for code to replicate, but moreover, the issues being described are nothing to do with nodemon.