Debugging with NODE_OPTIONS='--inspect=0.0.0.0' return error: /usr/bin/node: must be 0 or in range 1024 to 65535. #66189
Description
Link to the code that reproduces this issue
To Reproduce
Run:
NODE_OPTIONS='--inspect=0.0.0.0' next dev
Current vs. Expected behavior
Current:
> [email protected] dev
> NODE_OPTIONS='--inspect=0.0.0.0' next dev
Debugger listening on ws://0.0.0.0:9229/db48e9fb-b4a2-4600-ac6e-b339eb2c1337
For help, see: https://nodejs.org/en/docs/inspector
/usr/bin/node: must be 0 or in range 1024 to 65535.Expected:
Be able to set the NODE_OPTIONS --inspect with a custom IP and address.
Provide environment information
Operating System:
Platform: linux
Arch: arm64
Version: #1-TorizonCore SMP PREEMPT Thu Apr 11 16:18:46 UTC 2024
Available memory (MB): 3923
Available CPU cores: 4
Binaries:
Node: 18.20.3
npm: 10.7.0
Yarn: N/A
pnpm: N/A
Relevant Packages:
next: 14.2.3 // Latest available version is detected (14.2.3).
eslint-config-next: 14.2.3
react: 18.3.1
react-dom: 18.3.1
typescript: 5.4.5
Next.js Config:
output: standaloneOperating System:
Platform: linux
Arch: x64
Version: #1 SMP Wed May 15 19:51:07 -03 2024
Available memory (MB): 31915
Available CPU cores: 20
Binaries:
Node: 20.11.1
npm: 10.4.0
Yarn: 1.22.19
pnpm: N/A
Relevant Packages:
next: 14.2.3 // Latest available version is detected (14.2.3).
eslint-config-next: N/A
react: 18.3.1
react-dom: 18.3.1
typescript: N/A
Next.js Config:
output: standaloneWhich area(s) are affected? (Select all that apply)
Developer Experience, Instrumentation
Which stage(s) are affected? (Select all that apply)
next dev (local)
Additional context
Apparently, this should have been fixed with #59530
but the error remains the same.