feat: add deprecation warnings for invalid sendStatus parameters to prepare for Express v6 #6774
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.
Summary
Implements deprecation warnings for invalid status codes passed to
res.sendStatus()
, as recommended by maintainers. This provides a smooth migration path from the current throwing behavior to stricter validation planned for Express 6.Background
Previously,
res.sendStatus()
threw aTypeError
for non-number inputs. This PR introduces deprecation warnings for such inputs in Express 5, maintaining backward compatibility while preparing for Express 6, where these inputs will throw errors.Changes Made
depd
moduleundefined
,BigInt
, andstring
inputsString()
to safely convert invalid values in warningsBackward Compatibility
Test Results
All 1,242 tests pass, including the new comprehensive sendStatus test coverage validating fallback behavior and deprecation logic.
Implementation Details
depd
deprecation system consistent with other Express warnings