Node.js 26.12.0 stabilises its JSON config file flag
The flag renamed from --experimental-config-file to --config-file and is now stable, so node.config.json can set CLI options without NODE_OPTIONS or a wrapper script.
Node.js 26.12.0 shipped on 14 October and renames --experimental-config-file to --config-file, which is now Stable. The old flag, and --experimental-default-config-file, are kept as aliases so nothing already using them breaks.
The feature itself first landed experimental in v22.16.0: point Node at a JSON file, or let it find node.config.json in the working directory, and it applies the settings inside. Options are grouped by namespace, with nodeOptions covering anything normally passed through NODE_OPTIONS, plus dedicated sections for test, watch and permission. Command-line flags and environment variables still take priority over anything in the file.
{
"nodeOptions": {
"max-old-space-size": "4096",
"experimental-strip-types": true
}
}Why it matters: this is the difference between a config file you can rely on in CI and one you keep at arm’s length. Stable means Node won’t break the format inside a major version, so a committed node.config.json can finally replace the usual pile of wrapper scripts and exported NODE_OPTIONS for project-wide flags.