-
-
Notifications
You must be signed in to change notification settings - Fork 32.8k
doc: deprecate coercion to integer in process.exitCode
#44712
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
doc: deprecate coercion to integer in process.exitCode
#44712
Conversation
Signed-off-by: Daeyeon Jeong [email protected]
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it would make more sense to bundle this with DEP0164 as it is arguably the same thing.
A deprecation warning for |
I mean, we could still update the docs to clarify that both |
This warns of invalid uses of
process.exitCode
(such as mentioned in #43716 (comment)).In a quick search for
process.exitCode
below, I can't find invalid uses.However, I open this PR since it may need the doc-only deprecation first instead of throwing a validation error.
process.exitCode
isinteger
, but it should beinteger|undefined
. Its default value isundefined
.Refs: #43716
Refs: #43738
Signed-off-by: Daeyeon Jeong [email protected]