not working with Node.js version 20.12.x

[kireerik]

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 https://github.com/getsentry/sentry-javascript/issues/11453

[remy]

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

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

[remy]

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

[kireerik]

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

With 20.12.x it is not working.

[remy]

It is according to the directions you offered.

[kireerik]

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

[remy]

Also no.

[kireerik]

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.

[remy]

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).

[kireerik]

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

[remy]

No, it doesn't: https://github.com/remy/nodemon/issues/2194#issuecomment-2066755817

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

Last time I ask for details to replicate.

[kireerik]

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.

[remy]

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.