-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Upgrade showdown and do some lockfile gardening #21862
Conversation
Should we also update It's still at |
Size Change: -10.4 kB (1%) Total Size: 835 kB
ℹ️ View Unchanged
|
@gziolo Do you mean updating the version range from |
Yes, it will also ensure we publish a new patch version of the package (well, it would happend regardless for sure). It's definitely nice to have but it might be also a good practice to follow :) |
Sounds good, done! 🙂 |
All good, feel free to merge when Travis is green. |
@gziolo I think it's best if you take another look after the last commit, since there are now small unexpected changes in other packages. Travis isn't complaining any more about how running Thank you! |
Looks good 👍 |
Thanks again, @gziolo! |
Can you elaborate more on what was done here, and why? I'm encountering some issues in my pull request #21868 where I'm seeing "Build artifacts" that I'm unable to reproduce locally. I see almost all recent builds are failing as well. These changes seem particularly suspect. |
@aduth Right, that does sound unrelated, as far as I can tell. For reference, what I did was an After this, an Managing monorepos with |
Description
The
showdown
dependency was upgraded to the latest version, 1.9.1. This is a minor version, so it should be backwards compatible.The 1.9.x range is significantly smaller than the currently used version, 1.8.6, by about 20KB uncompressed, or 9KB gzipped.
In addition, I performed some gardening on the lockfile, reducing duplicate dependencies by reusing the same version where the ranges allow.
This PR as a whole should save around 23KB uncompressed (9KB gzipped) in the blocks chunk, and a much tinier 3 KB uncompressed (860B) in the components chunk, without any code changes. I guess the GitHub action will tell!
How has this been tested?
Ran build, ran unit tests, performed ad-hoc testing of editor.
Types of changes
Dependency upgrades and lockfile management only.
Checklist: