-
Notifications
You must be signed in to change notification settings - Fork 558
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
Testing using WordPress Components #2808
base: trunk
Are you sure you want to change the base?
Conversation
looks like the |
…vled a number of other dependancy updates and some config changes.
…the updated version
I took a stab at upgrading webpack to the latest version. That involved upgrading other plugins and dependencies. It also involved adding in some other dependencies and config updates to get everything building properly. |
…ss/components and a custom progress bar
I figured out what was wrong with one of my previous updates and not having source maps set correctly. I've updated the main description with size details. |
With @dmsnell's help I have webpack bundle anayzler now looking at the gzipped sizes of our bundle. |
Just for personal testing currently.
This currently updated the Note Info panel on the right to use the WordPress Toggle Control instead of our previous component and removes Material UI.
The changes were pretty straightforward and with some basic styling was able to get the components to look the same as our current designs.
It also adds Webpack Bundle Analyzer to check things out. To run you can now run the following two commands.
npm run stats
generates the stats file.npm run analyzer
which will start the bundle analyzer so you can view.Build size differences
Current 2.9.0 build:
This build with WP Components:
Webpack bundle analyzer gzipped sizes