build: Exclude experimental pages from Core builds#76038
Merged
youknowriad merged 2 commits intotrunkfrom Mar 4, 2026
Merged
Conversation
Allow pages to be marked as 'experimental' in package.json, and filter them out when IS_WORDPRESS_CORE env var is set during build. The site-editor-v2 page is now marked as experimental. When building for WordPress Core (IS_WORDPRESS_CORE=true), experimental pages and their routes are excluded from the build output. Implementation: - Add 'experimental' flag to page definitions in wpPlugin.pages - Preserve the flag during page normalization in build.mjs - Filter out experimental pages and their routes when IS_WORDPRESS_CORE is truthy - Update route registry and route PHP generation to use filtered routes Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
Size Change: 0 B Total Size: 6.87 MB ℹ️ View Unchanged
|
gutenbergplugin
pushed a commit
that referenced
this pull request
Mar 4, 2026
|
I just cherry-picked this PR to the wp/7.0 branch to get it included in the next release: ba8547f |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What?
Allow pages to be marked as
experimentalinpackage.json, and filter them out when building for WordPress Core.Why?
The
site-editor-v2page is experimental and should not be included in WordPress Core builds. This change provides a mechanism to exclude experimental pages by setting theIS_WORDPRESS_COREenvironment variable during the build process.How?
experimental: trueflag to page entries inwpPlugin.pagesIS_WORDPRESS_COREis truthyThe change is backward-compatible: existing pages without the flag default to non-experimental and are always included.
Testing Instructions
npm run build— site-editor-v2 should be included as usualIS_WORDPRESS_CORE=true npm run build— site-editor-v2 pages/routes should be excluded from outputbuild/pages/site-editor-v2/does not exist when building withIS_WORDPRESS_CORE=truebuild/routes/registry.phpin Core builds