René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Multiple --env-file no longer work with --watch","articleBody":"### Version\n\nv25.1.0\n\n### Platform\n\n```text\nMicrosoft Windows NT 10.0.26200.0 x64\n```\n\n### Subsystem\n\n_No response_\n\n### What steps will reproduce the bug?\n\n1. Create .a.env, and .b.env.\n2. .a.env includes: \"ENV_VAR_A=123\".\n3. .b.env includes: \"ENV_VAR_B=456\".\n4. create index.js that does this:\n```\nconsole.log(process.env.ENV_VAR_A)\n```\n5. Run \"node --env-file=.a.env --env-file=.b.env --watch index.js\".\n6. Result output \"undefined\" (instead of 123)\n\n### How often does it reproduce? Is there a required condition?\n\nAlways\n\n### What is the expected behavior? Why is that the expected behavior?\n\nExpected to see \"123\", because both .env files should be included and loaded as the command says. Notice that the env vars in those 2 files are different, so those 2 files should be \"merged\" as result, instead of be completely overwritten by the last one.\n\n### What do you see instead?\n\nIt always output \"undefined\" when \"--watch\" is added. It does output \"123\" when \"--watch\" is removed.\n\n### Additional information\n\nUntil Node.js v24.4, the multiple --env-file works well with --watch. I updated to v25.1.0 yesterday, and this pattern no longer works. As I've mentioned above, highly likely this is caused by \"--watch\" flag.","author":{"url":"https://github.com/tclzcja","@type":"Person","name":"tclzcja"},"datePublished":"2025-11-06T03:43:27.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":3},"url":"https://github.com/60599/node/issues/60599"}