adding multiple NODE_OPTIONS(--openssl-legacy-provider --max_old_space_size) is not working

[arunvenkat1911]

Details

HI Team,

I am trying to set these multiple options.

"scripts":{
"build":"set NODE_OPTIONS='--openssl-legacy-provider --max_old_space_size=8192' && webpack serve --open --config ../webpack.config.js --progress"
}

it is not working as expected. Attached the error image.

NOTE: when we try the options individually, they are fine.

Please help me with the solution.

Arun.

Node.js version

18.2.1

Example code

No response

Operating system

windows 11

Scope

runtime

Module and version

Not applicable.

[bmuenzenmeyer]

I've tried to make a minimal recreation of this. Some observations:

Node.js version

18.2.1

There is no 18.2.1 version of Node.js per https://nodejs.org/en/download/releases/ and nvm

Using 18.12.1 as an approximation.

NOTE: when we try the options individually, they are fine.

I am making an assumption that all flags are applied equally. I picked two that are easy enough to eval in a one liner:

{
  "name": "4047",
  "version": "1.0.0",
  "description": "",
  "scripts": {
    "start": "node --eval 'console.log(Object.prototype.__proto__);process.exit(0)'",
    "start:1:disable-proto": "NODE_OPTIONS='--disable-proto=throw' node --eval 'console.log(Object.prototype.__proto__);process.exit(0)'",
    "start:1:trace-exit": "NODE_OPTIONS='--trace-exit' node --eval 'console.log(Object.prototype.__proto__);process.exit(0)'",
    "start:both": "NODE_OPTIONS='--disable-proto=throw --trace-exit' node --eval 'console.log(Object.prototype.__proto__);process.exit(0)'"
  },
  "keywords": [],
  "author": "BrianMuenzenmeyer",
}

npm start

> 4047@1.0.0 start
> node --eval 'console.log(Object.prototype.__proto__);process.exit(0)'

null

✅ control, no NODE_OPTIONS

npm run start:1:disable-proto

> 4047@1.0.0 start:1:disable-proto
> NODE_OPTIONS='--disable-proto=throw' node --eval 'console.log(Object.prototype.__proto__);process.exit(0)'

[eval]:1
console.log(Object.prototype.__proto__);process.exit(0)
                             ^

Error: Accessing Object.prototype.__proto__ has been disallowed with --disable-proto=throw
    at [eval]:1:30
    at Script.runInThisContext (node:vm:129:12)
    at Object.runInThisContext (node:vm:313:38)
    at node:internal/process/execution:79:19
    at [eval]-wrapper:6:22
    at evalScript (node:internal/process/execution:78:60)
    at node:internal/main/eval_string:28:3 {
  code: 'ERR_PROTO_ACCESS'
}

Node.js v18.12.1

✅ errors on usage, mentions the NODE_OPTION

npm run start:1:trace-exit

> 4047@1.0.0 start:1:trace-exit
> NODE_OPTIONS='--trace-exit' node --eval 'console.log(Object.prototype.__proto__);process.exit(0)'

null
(node:72567) WARNING: Exited the environment with code 0
    at exit (node:internal/process/per_thread:195:13)
    at [eval]:1:49
    at runInThisContext (node:vm:129:12)
    at runInThisContext (node:vm:313:38)
    at node:internal/process/execution:79:19
    at [eval]-wrapper:6:22
    at evalScript (node:internal/process/execution:78:60)
    at node:internal/main/eval_string:28:3

✅ completes the entire program, prints trace info (exit code 0)

npm run start:both

> 4047@1.0.0 start:both
> NODE_OPTIONS='--disable-proto=throw --trace-exit' node --eval 'console.log(Object.prototype.__proto__);process.exit(0)'

[eval]:1
console.log(Object.prototype.__proto__);process.exit(0)
                             ^

Error: Accessing Object.prototype.__proto__ has been disallowed with --disable-proto=throw
    at [eval]:1:30
    at Script.runInThisContext (node:vm:129:12)
    at Object.runInThisContext (node:vm:313:38)
    at node:internal/process/execution:79:19
    at [eval]-wrapper:6:22
    at evalScript (node:internal/process/execution:78:60)
    at node:internal/main/eval_string:28:3 {
  code: 'ERR_PROTO_ACCESS'
}

Node.js v18.12.1
(node:75235) WARNING: Exited the environment with code 1

✅ error on usage, prints additional trace info (node:75235) WARNING: Exited the environment with code 1

---

I'll try to test this on my Windows machine too, but for now it seems as if both NODE_OPTIONS flags are being respected

[preveen-stack]

I'll try to test this on my Windows machine too, but for now it seems as if both NODE_OPTIONS flags are being respected

@bmuenzenmeyer were you able to check this on your windows machine

[github-actions]

It seems there has been no activity on this issue for a while, and it is being closed in 30 days. If you believe this issue should remain open, please leave a comment.
If you need further assistance or have questions, you can also search for similar issues on Stack Overflow.
Make sure to look at the README file for the most updated links.

[github-actions]

It seems there has been no activity on this issue for a while, and it is being closed. If you believe this issue should remain open, please leave a comment.
If you need further assistance or have questions, you can also search for similar issues on Stack Overflow.
Make sure to look at the README file for the most updated links.