-
Notifications
You must be signed in to change notification settings - Fork 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
Update @wordpress/components #65576
Update @wordpress/components #65576
Conversation
87ae168
to
7e3172b
Compare
Here is how your PR affects size of JS and CSS bundles shipped to the user's browser: App Entrypoints (~2677 bytes added 📈 [gzipped])
Common code that is always downloaded and parsed every time the app is loaded, no matter which route is used. Sections (~1361 bytes removed 📉 [gzipped])
Sections contain code specific for a given set of routes. Is downloaded and parsed only when a particular route is navigated to. Async-loaded Components (~3393 bytes added 📈 [gzipped])
React components that are loaded lazily, when a certain part of UI is displayed for the first time. Legend What is parsed and gzip size?Parsed Size: Uncompressed size of the JS and CSS files. This much code needs to be parsed and stored in memory. Generated by performance advisor bot at iscalypsofastyet.com. |
- Updated components package 19.11.0 => 19.15.0 - Used `yarn dedupe` to ensure only a single version in the mono repo I didn't update the 3rd-party types package (i.e. @types/wordpress__components) because it caused peer-dependency errors.
`yarn` doesn't appear to have an `upgrade` sub-command. The `up` sub-command does the same thing though.
7e3172b
to
173678e
Compare
This PR modifies the release build for editing-toolkit To test your changes on WordPress.com, run To deploy your changes after merging, see the documentation: PCYsg-mMA-p2 |
Discussion about the failing audio upload test: p1657741571341949-slack-C03N25JPCE4 |
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.
cc'ing @dmsnell re. the createHigherOrderComponent
code changes (originated from WordPress/gutenberg#41138), since Jarda is not around
For the smoke test, I'll let folks with greater familiarity with Calypso take a look
The rest of the code changes LGTM
Nice. I saw the |
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.
I wonder if the failing e2e tests are related 🤔
@ciampo what kind of review are you looking for? |
Apologies if that wasn't clear! Mainly focused on the code changes regarding |
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.
From the perspective of the types this is fine. If they work for you then they are fine, and it looks like they work as I remember those functions intending.
@tyxla the test failures were unrelated and the underlying issue has been fixed p1657741571341949-slack-C03N25JPCE4 |
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.
Haven't tested but code-wise this looks good 👍
I've tested ETK and areas of Calypso using WordPress components and everything seems to be working. No console errors etc. 🤞 |
Currently we can't import
@wordpress/components
in some places, because if it's ever imported into a file that's used during unit tests, then it will break the tests. This is a bug in the package which was addressed in WordPress/gutenberg#42248. This PR updates the version of the package used by Calypso so it canChangelog for the component package, the relevant notes are for versions
19.12.0
through19.15.0
. There have been enhancements to the components we use, but bigger changes (like the updated design for theDateTimePicker
) only impact our custom blocks, and those blocks will be using the sharedwp.components
version of the package anyway.Proposed Changes
yarn dedupe
to ensure only a single version in the mono repowithInstanceId()
andcreateHigherOrderComponent()
which have had their type definitions changeIt doesn't update the 3rd-party types package (i.e.
@types/wordpress__components
) because doing so creates yarn errors and it's not needed to address the issue we're facing.Testing Instructions
Pre-merge Checklist
Complete applicable items on this checklist before merging into trunk. Inapplicable items can be left unchecked.
Both the PR author and reviewer are responsible for ensuring the checklist is completed.
Have you written new tests for your changes?Are we memoizing when appropriate (for expensive computations)? More info in Our Approach to Data and Memoizing with create-selector and Using memoizing selectorsHave we sent any new strings for translation ASAP?