Repository navigation
Scripts: Allow a custom output path for --blocks-manifest - #83876
Open
Mayank-Tripathi32 wants to merge 3 commits into
Open
Mayank-Tripathi32 wants to merge 3 commits into
Mayank-Tripathi32 wants to merge 3 commits into
Conversation
start and build always wrote the manifest to the webpack output folder. Accept --blocks-manifest=<path> and pass it on as --output. The bare flag keeps the current behaviour. See WordPress#70694.
Mayank-Tripathi32
added
[Type] Enhancement
Mayank-Tripathi32
marked this pull request as ready for review
September 30, 2026 12:40
|
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. |
This branch has not been deployed
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?
Closes #70694
wp-scripts buildandwp-scripts startnow accept a path for--blocks-manifest, e.g.--blocks-manifest=dist/blocks-manifest.php. A bare--blocks-manifestworks as before.Why?
The manifest was always written to
blocks-manifest.phpin the webpack output folder. Only the standalonebuild-blocks-manifestcommand accepted--output, so projects that keep the manifest elsewhere couldn't use the flag withbuildorstart.How?
getWebpackArgs()reads the value of--blocks-manifest=<path>and stores it inWP_BLOCKS_MANIFEST_OUTPUT, next to the existingWP_BLOCKS_MANIFEST.build-blocks-manifestas--output.--output.I gave the existing flag a value instead of adding a separate
--output-blocks-manifestflag (suggested in the issue), so it works like--source-path=and there's one flag to learn.Testing Instructions
In a block plugin created with
@wordpress/create-block:npx wp-scripts build --blocks-manifest=dist/blocks-manifest.php: the manifest is written todist/, notbuild/.npx wp-scripts start --blocks-manifest=dist/blocks-manifest.php, then edit ablock.json: the manifest indist/is regenerated.npx wp-scripts build --blocks-manifest: still writesbuild/blocks-manifest.php.Unit tests:
npm run test:unit -- packages/scripts/utils/test/index.jsTesting Instructions for Keyboard
No UI changes.
Use of AI Tools
Yes, Opus is used for implementation.