Repository navigation
v20.19.0 release notes - outdated messaging #57517
Description
Activity
Probably a mistake but I'll leave Joyee to re-word and then I'll update the release notes
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-moduleis 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?)
correct, thats it
- added a commit that references this issue
on Mar 19, 2025 - added a commit that references this issue
on Mar 22, 2025 - added 2 commits that reference this issue
on May 1, 2025
Regarding this sentence in https://github.com/nodejs/node/releases/tag/v20.19.0
This is not true in v20.19.0 due to
Test.mjsmain.cjs$ node main.cjs v20.19.0 [Module: null prototype] { __esModule: true, default: [class Test] }Am I missing the point of the original sentence?