Block editor broken — Jetpack 15.9-a.3 bundled private-apis conflicts

• 

  evanthomasking · Member · May 21, 2026 at 7:07 pm

  • Copy link
  • Add topic to favorites

  Since approximately May 19, 2026, the Gutenberg block editor fails to load on all posts and pages. Browser console shows:
  • private-apis.min.js: Error: @wordpress/theme is not a registered private access module
  • private-apis.min.js: Error: @wordpress/upload-media which is already registered
  • data.min.js: Store “jetpack-connection” is already registered (appears 5+ times)
  My site was placed on Jetpack 15.9-a.3 (alpha build, 2026-05-19). This build bundles its own copy of @wordpress/private-apis compiled against WP 6.x — this was intentionally introduced in 15.8 per your own changelog: “Bundle WordPress private-apis and theme packages in the admin script so dependencies enqueue reliably on all hosts.”
  WordPress 7.0 changed the private-apis lock key and added @wordpress/theme and @wordpress/upload-media to CORE_MODULES. Jetpack 15.9-a.3’s bundled copy was built before these changes. When both load, Jetpack’s old bundled private-apis wins the global window.wp.privateApis registration, and WP 7.0 core’s theme.min.js crashes immediately because @wordpress/theme isn’t in the old CORE_MODULES list.
  Steps to reproduce: Edit any post or page → block editor fails to load → browser console shows the errors above.

  The blog I need help with is: (visible only to logged in users)