-
Notifications
You must be signed in to change notification settings - Fork 778
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
chore(deps): package-lock maintainance #4621
chore(deps): package-lock maintainance #4621
Conversation
Whoa, a 41k line change to package-lock? |
Ah, something must've gone wrong - I actually just ran |
I see that in #4601 part of the change to package-lock included this:
I don't know that that is problematic, but it is weird. |
package-lock and npm workspaces sure are a ride. |
I think I know why this happens: It must be the prepare release script, we remove the API there so that lerna can do it's thing. We'll likely need to sync package-lock again after we do that. |
#4623 should take care of this. |
I tried that too, and my diff is 72k! :)
I don't really know what to say. I think the huge diff is from shuffling around where deps are installed. E.g. in my 72k line diff, all the mocha@10 deps were shuffled from the top-level I guess we just take it and move on. |
New highscore :D
I'll try to enable packge-lock maintainance on renovate bot. Maybe it can manage to produce a diff that's a bit less daunting to look at. 🤔 |
PR to enable lock file maintenance, let's see what it does: #4628 🙂 |
Closing this for now as I think going the renovate route will be better. |
Updates dependencies in
package-lock.json
, first commit is actually #4620. This will be rebased once it's merged.