-
Notifications
You must be signed in to change notification settings - Fork 73
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
Don't normalize package.json fields #1143
Don't normalize package.json fields #1143
Conversation
📦 Package Size: 5448 KB |
f235959
to
3710ea1
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1143 +/- ##
==========================================
+ Coverage 69.44% 70.05% +0.60%
==========================================
Files 202 202
Lines 7335 7336 +1
Branches 1284 1299 +15
==========================================
+ Hits 5094 5139 +45
+ Misses 2218 2174 -44
Partials 23 23 ☔ View full report in Codecov by Sentry. |
3710ea1
to
e9d7fa8
Compare
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.
What else does normalization do? Are we using any of it?
It does a bunch of stuff but it doesn't appear we use any of it (I could be wrong though). |
🚀 PR was released in |
Fixes #1123
This fixes a weird bug where an invalid semver string in the
version
field of a user'spackage.json
causes the CLI to silently exit. Turns out, it comes from normalizing thepackage.json
file fromread-package-up
andmeow
. This disables that behavior to prevent this issue.📦 Published PR as canary version:
11.25.2--canary.1143.12912030314.0
✨ Test out this PR locally via: