fix: envInt returns NaN for non-numeric env vars - #410
Open
fix2015 wants to merge 2 commits into
Open
Conversation
parseInt("abc", 10) returns NaN which propagated as a valid number
through the config system — setting PORT=abc would try to listen on
port NaN. added isNaN check so non-numeric values are skipped.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
`envInt` was calling `parseInt(val, 10)` and returning the result directly, but `parseInt("abc", 10)` returns `NaN`. That `NaN` would propagate through the config as a valid number — setting `PORT=abc` would cause the HTTP server to try to listen on port `NaN`, producing a confusing error deep in Node's net module instead of a clear validation message.
Added an `isNaN` check so non-numeric environment variables are skipped and the default value is used instead.