Yet Another Config File: introducing node.config.json
summary
Node.js v23 adds node.config.json as an experimental runtime config file parsed automatically from the project root or via an explicit path and guarded by an experimental flag it stores structured flags, a JSON schema for IDE autocomplete, and namespaces such as testrunner namespace that enable options previously unavailable in NODE_OPTIONS some CLI and V8 flags remain disallowed conflicts resolve by CLI > NODE_OPTIONS > config file > NODE_OPTIONS from m the JSON parser is a fast cmd_json C++ parser and startup cost increases only trivially while debates continue about using package.json instead of a separate file
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:07Node.js evolution
- 3:17Configuring Node.js challenges
- 6:25Environment variables limits
- 9:14Need for config file
- 12:05Introducing node.config.json
- 15:37Restrictions and capabilities of node.config.json
- 18:35Test runner config namespace
- 20:20Performance impact
- 21:48Publishing on npm
- 23:11Future plans
- 24:38Controversy
related talks
18mEverything-as-Code: It's time to fix configurations
22mZero-dependency CLI Applications with Node.js
27m10 Things I Regret About Node.js
32mPlease Wait... Loading: A Talk of Two Loaders
29mNode.js: The New and the Experimental
27mBuilt-in Tests with Node.js
17mHow Node.js Bootstraps Itself: 2019 Edition
26mZero-dependency CLIs with Node.js