-
Notifications
You must be signed in to change notification settings - Fork 2.9k
refactor(npm): lockfile extraction code #7703
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
Conversation
viceice
left a comment
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.
Just one Question: Why switch to undefined instead of existing NaN ? Otherwise LGTM
viceice
left a comment
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.
tested NaN vs undefined
undefined < 6 === false
undefined > 6 === false
NaN > 6 === false
NaN < 6 === falsejust a small type change
Co-authored-by: Michael Kriese <[email protected]>
|
🎉 This PR is included in version 23.83.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Changes:
Refactored lockfile extraction code.
Context:
For #7700
Documentation (please check one with an [x])
How I've tested my work (please tick one)
I have verified these changes via: