-
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
wpcom-proxy-request: Return Promise if no callback specified (Take Two) #39722
wpcom-proxy-request: Return Promise if no callback specified (Take Two) #39722
Conversation
Here is how your PR affects size of JS and CSS bundles shipped to the user's browser: App Entrypoints (~315 bytes added 📈 [gzipped])
Common code that is always downloaded and parsed every time the app is loaded, no matter which route is used. 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. |
74918ee
to
0906388
Compare
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.
Let's try again!
Take Two of #39683. Reverts #39721.
npm run distclean && npm ci && npm run build-docker
.Original PR desc:
Changes proposed in this Pull Request
The promise wrapper introduced by @andrewserong et al. in #38823 seems generic enough for it to make sense to have it in
wpcom-proxy-request
. This PR moves it there. This follows precedent set bywpcom.js
.Note that this is a technically a breaking change, as noted in the package's
History.md
:Testing instructions
Verify that Gutenboarding still works (esp account and site creation).