Repository navigation
docs: follow up on the review notes from #842 and #844 - #845
Merged
Merged
Conversation
Adi-ty
approved these changes
Nov 10, 2026
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 this PR does
Picks up Aditya's notes on #842 and #844, which merged without them so the 2.0.1 release could go out tonight. Docs and comments only, no behaviour change.
Changes
webpack.blocks.config.jsanddocs/hmr.mdsaid the wrapper exists because webpack-dev-server v5, pinned throughoverrides, rejects the object-formproxywp-scripts emitted. Since fix(deps): update @wordpress/scripts to 37 and refresh stale npm overrides #842 that pin is gone and wp-scripts 37 runs webpack-dev-server 6 with an array-form proxy. The wrapper still removes it, for a different reason: the/buildproxy target is hardcoded tolocalhost:8887, so with a customBLOCKS_DEV_SERVER_PORTit points at another server. The comments and docs now say that.docs/hmr.mdalso saidallowedHosts: 'all'is set. The wrapper limits it tolocalhostandWP_HOST; the line now matches the code and the plugin's docs.README.md,.claude/skills/README.md,docs/initialization.mdanddocs/internal/maintenance.mdno longer say thetaskandepicissue templates stay after init, since chore: drop the duplicate security link and the Epic and Task templates #844 removed them.How I verified
@wordpress/scripts37.0.0'sconfig/webpack.config.js: the dev server'sproxyis[ { context: [ '/build' ], target: 'http://localhost:8887', ... } ].package-lock.jsononmainresolveswebpack-dev-server6.1.0, with no override.node --check webpack.blocks.config.js; only comments changed in it.git grepfinds no other mention of the removed templates or of webpack-dev-server v5.