Version

24.3.0

Platform

macOS Arm

Subsystem

No response

What steps will reproduce the bug?

1. Create a file leveraging an experimental feature (ex module mocks)
2. Run the file via CLI with the --no-warnings flag
   1. Notice no experimental warning is printed
3. Remove the flag from the CLI command, and add "warnings: false" to node.config.json (and include via that CLI flag)
   1. Notice an experimental warning IS printed

How often does it reproduce? Is there a required condition?

100%

What is the expected behavior? Why is that the expected behavior?

nodeOptions.warnings: false behaves the same as its CLI flag --no-warnings

What do you see instead?

Warnings

Additional information

No response