Block and Component Lazy Loading #2768
Description
- Part of Block API #41236
Tasks List
- Blocks: move bootstrapped block types to Redux state #53807
- Blocks: Allow reading the script handle from asset files wordpress-develop#5118
- Block lazy loading #51778
Issue Overview
Initially raised by @mtias in #665 and something that @dmsnell has already started exploring when working on CodeMirror block. It would be beneficial to have a standardized way to defer loading optional parts of the block and/or the whole block in general when it is resource heavy. I might even risk saying that it would make sense to have all external blocks by default loaded on demand using chunk splitting technique. It would help us ensure that only essential parts of Gutenberg are loaded on initial page load, which would lead to better performance and overall first-time impression. We could start pre-loading optional blocks when the browser is idle or whenever a user is about to select such block using the drop-down menu or / command. All that should help scale Gutenberg as the number of available blocks grows.
Related Issues, PRs and discussions
- Introduce new CodeMirror block for editing code. #665
- Expose available blocks via an API #4116
- FR: Async fetching prior to block registration #12232
- Add script and style REST APIs #21244 (https://core.trac.wordpress.org/ticket/48654)
- Try: Simple async block loading #48315
- Block lazy loading #51778
- Block lazy loading #53260