doc: fix deprecation documentation inconsistencies #35082
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've noticed a few inconsistencies between
deprecations.md
and other doc files:domain.md
doesn't indicate in which version its deprecation was introduced (https://nodejs.org/docs/latest/api/deprecations.html#DEP0032).EventEmitter.listenerCount
indicates a deprecation introduced inv4.0.0
inevents.md
, but it'sv3.2.0
according todeprecations.md
(https://nodejs.org/docs/latest/api/deprecations.html#DEP0033).fs.lchown
[Sync
] indicates when its deprecation was revoked, but not when it was assigned infs.md
(https://nodejs.org/docs/latest/api/deprecations.html#DEP0037 & https://nodejs.org/docs/latest/api/deprecations.html#DEP0038).punycode.md
indicates a runtime deprecation, but instead it's a documentation-only deprecation (https://nodejs.org/docs/latest/api/deprecations.html#DEP0040).Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passes