-
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
Upgrade WordPress monorepo #48729
Upgrade WordPress monorepo #48729
Conversation
Here is how your PR affects size of JS and CSS bundles shipped to the user's browser: Webpack Runtime (~14 bytes removed 📉 [gzipped])
Webpack runtime for loading modules. It is included in the HTML page as an inline script. Is downloaded and parsed every time the app is loaded. App Entrypoints (~9098 bytes added 📈 [gzipped])
Common code that is always downloaded and parsed every time the app is loaded, no matter which route is used. Sections (~150250 bytes added 📈 [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 (~39133 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. |
Yep, they can be removed for any packages that include types. DefinitelyTyped has a process for removing types for packages that no longer require them which I usually do periodically, but maybe @saramarcondes would like to help as well. |
72f52cd
to
7fad162
Compare
OK, I removed the type packages, except |
The There is no longer a The @noahtallen @vindl What is a good way to test the upgrade here and can you possibly help? I don't really know what I'm doing when touching these parts of the codebase. |
7fad162
to
e79b5a3
Compare
Caution: This PR affects files in the Editing Toolkit Plugin on WordPress.com D55058-code has been created so you can easily test it on your sandbox. See this FieldGuide page about developing the Editing Toolkit Plugin for more info: PCYsg-ly5-p2 |
e79b5a3
to
80b1790
Compare
Turns out most |
80b1790
to
3cca9fe
Compare
To get these changes on your wpcom sandbox, you have two options:
Then just sandbox a test site and the public API, and all the changes will appear when you visit the editor of that sandboxed site :) I'm also happy to test these out! |
ecc1946
to
4ca09ac
Compare
While testing the Editing Toolkit on my sandbox, I discovered the color changes (forced by The selected background color is too light. So I decided to use the original colors everywhere, and declare local variables with the values that are no longer in |
64cc536
to
f7f540c
Compare
@vindl I had to remove the Is there such a thing as Full Site Editing embedded in Calypso Gutenframe? Doing the check on that page would make it work. |
@jsnajdr there is, but it's basically using the existing iframe post editor setup and just feeding it the different wp-admin url. |
f2eba36
to
a6f3dc8
Compare
I disabled the Gutenboarding e2e test for now (cc @Automattic/luna). That made all checks green and I can finally merge this one (ufff). |
A fresh attempt to land changes from #46223.
Upgrades all
@wordpress/*
packages except@wordpress/scripts
. That package triggers a Babel update, too, and causes too many changes inyarn.lock
. We can do it in a separate PR.The upgrades packages are deduplicated.
Contains all the SASS color name changes from #46223 caused by
@wordpress/base-styles
upgrade, squashed into one commit.Contains my unit test fixes and also @sirreal's
react-i18n
typing upgrades.@sirreal one thing I'm not 100% sure about: the new
@wordpress/*
packages all have published types. Does that mean we can remove all@types/wordpress__*
dependencies now? They should be redundant.Fixes #48585