-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Refactor NpmLockfileUpdater #3112
Conversation
@@ -1,11 +1,11 @@ | |||
{ | |||
"name": "{{ name }}", | |||
"name": "project-name", |
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.
This is more realistic example where the lockfile has a "valid" generated name by some build step, we make sure to restore this name, not the invalid name in the package.json
, the code to restore this hasn't changed
Extracting a refactor from #3106 Initialize the lockfile updater with a lockfile being updated removing the need to pass around the lockfile everywhere. A few spec changes have snuck in from the above pr but these should be cosmetic as no fuctionality has changed.
0cd7ae2
to
448fbce
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.
This looks great, thanks for pulling it out!
Extracting a refactor from
#3106
Initialize the lockfile updater with a lockfile being updated removing
the need to pass around the lockfile everywhere.
A few spec changes have snuck in from the above pr but these should be
cosmetic as no fuctionality has changed.