Have a topic for discussion for the next meeting? Leave a suggested edit on next week’s agenda.
Agenda: Shared Core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Dependencies
The Google Doc Agenda has much of the content of what was discussed, but as a summary:
wp.element on the frontend. It has a dependency on lodash which adds weight to page load.
- implementing various components or blocks on the frontend (
wp.components itself has significant size).
Some potential ways to resolve/improve this for not only frontend but also admin (and super admin) are:
Load externals via CDN.
Externals such as
lodash etc could still be registered but the source would be from CDN. The advantage here is with WP’s wide reach, it’s much more likely that client browsers will have cached the asset for visitors to WP sites. Currently that’s less likely because of every site hosting it’s own assets by default.
Action: @adamsilverstein is going to raise this in the hosting meeting to get feedback from there.
Size of packages.
Here, the focus is on how big are we willing to allow various bundles to get? For instance
wp.components is 553kB minified.
- should we start thinking about setting some comfortable limits on how big we allow bundles to get? (tools like bundlesize could help with that)
- what ways can bundles be further reduced in size (example of
@wordpress/server-side-render being extracted into it’s own package) – audit packages and see what other extractions/groupings can be done?
- WP core supports script-aliases (enqueuing
wp-components could actually enqueue X different files behind the scenes, all populating the
- Reduce external dependencies: Example is lodash dependency removal from
@wordpress/element. Much of the functionality of lodash can be implemented via native js.
- On the last item, removing lodash dependency from WordPress packages has been proposed. It’d be nice to get a decision on moving forward there. Please contribute your thoughts to the issue!
Agenda: Lazy Loading of Images and Frames
Slack | Trac | lazysizes library | Native lazy-loading for the web article
The discussion here centered around whether lazy loading of images is something that should be implemented in WordPress core and some initial ideas on what would be involved in doing that. Some highlights of the discussion (though no concrete decision was made):
- opt-in for now
- possibly implemented via
- include for wp-admin as well (eg. Media Library)
- continue to contribute to the trac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. ticket Created for both bug reports and feature development on the bug tracker.. Possibly explore landing something for wp-admin first.