v20.19.0 release notes - outdated messaging

[alexsch01]

Regarding this sentence in https://github.com/nodejs/node/releases/tag/v20.19.0

When the Node.js instance encounters a native ES module in require() somewhere outside node_modules for the first
time, it will emit an experimental warning unless require() comes from a path that contains node_modules.

This is not true in v20.19.0 due to

[[de313b2336](https://github.com/nodejs/node/commit/de313b2336)] - (SEMVER-MINOR) module: only emit
require(esm) warning under --trace-require-module (Joyee Cheung) https://github.com/nodejs/node/pull/56194

---

Test.mjs

export default class Test {}

main.cjs

console.log(process.version, require('./Test.mjs'))

---

$ node main.cjs
v20.19.0 [Module: null prototype] { __esModule: true, default: [class Test] }

---

Am I missing the point of the original sentence?

[aduh95]

/cc @marco-ippolito @joyeecheung

[marco-ippolito]

Probably a mistake but I'll leave Joyee to re-word and then I'll update the release notes

[joyeecheung]

Ah, yes, I wasn't thinking straight and got stuck with an older status when I proposed the changes to the release notes, sorry. The latest status should just be:

This feature has been tested on v23.x and v22.x, and we are looking for user feedback from v20.x to make more final tweaks before fully stabilizing it. It now no longer emits a warning unless --trace-require-module is explicitly used. If there happens to be any regressions caused by this feature, users can report it to the Node.js issue tracker. Meanwhile this feature can also be disabled using --no-experimental-require-module as a workaround.

Should I just update the changelog_v20.md and sync the rest (what are the rest, apart from the GitHub release notes and the blog?)

[marco-ippolito]

correct, thats it