chore: Update package dependencies / package-locks #4191
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I happened to need to nuke my
packages/*/node_modules
before releasing today, and noticed that in the process, some package-lock files changed. This in turn led me to canvas for issues in our package-locks.What I found / what this PR fixes:
Note that I'm running npm 6.5.0; it's possible that some of these changes (in particular the changes to mdc-dialog and mdc-drawer) have to do with npm updates, but it's also possible they were simply the result of cleaning out
packages/*/node_modules
.