-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Fix package id in shrinkwrap lifecycle step output #288
Conversation
e613715
to
3c7d80e
Compare
Currently all logging related to shrinkwrap steps reports 'undefined' for the package in output and log messages. This is due to the package associated with the `idealTree` being recreated in the `savePackageJson()` method which precedes these steps. For now, just copy forward the `_id` attribute which lifecycle logging expects, but note that mutating `package` here is surprising. Fixes npm/npm#20756
3c7d80e
to
38d91de
Compare
Not supported on node 6 apparently. Can get the same effect by explictly matching the newline character.
@ruyadorno @claudiahdz Is there anything I can do to help get this reviewed and landed? What kind of discussion is needed exactly? This is a pretty simple change that improves error output for steps after post install. |
This looks good to me. It's irrelevant in npm v7, but we may as well fix this little thing in the meantime. Sorry for the delay, we're all pretty focused on getting the next major done. Thanks for your patience. |
@claudiahdz It it possible for you to merge this? I do not have write access to actually land. @isaacs Thank you for the review. I like the streamlined upcoming changes, though it now doesn't say which script has failed:
|
This will be added on |
Currently all logging related to shrinkwrap steps reports 'undefined'
for the package in output and log messages.
This is due to the package associated with the
idealTree
beingrecreated in the
savePackageJson()
method which precedes thesesteps. For now, just copy forward the
_id
attribute which lifecyclelogging expects, but note that mutating
package
here is surprising.Fixes npm/npm#20756