Skip to content

Docs: add the wp-build porting checklist #52578

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
CGastrell merged 5 commits into from
Sep 22, 2026
Merged

Docs: add the wp-build porting checklist #52578

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
62c005b
Add the wp-build porting checklist
CGastrell Sep 21, 2026
aa948b6
Checklist: unwrap, fix the dashboard count and two section cross-refe…
CGastrell Sep 21, 2026
3e2b424
Checklist: correct the boot-bump attribution and two fix-vs-regressio…
CGastrell Sep 21, 2026
6679bef
Checklist: fix the §8 attribution and link the doc from monorepo.md
CGastrell Sep 21, 2026
27db12e
Checklist: apply the review
CGastrell Sep 22, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions docs/monorepo.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -164,6 +164,7 @@ A project must define `.scripts.build-development` and/or `.scripts.build-produc
The build commands should assume that `pnpm install` and `composer install` have already been run, and _must not_ run them again.

* If you're building JavaScript bundles with Webpack and [@automattic/jetpack-webpack-config](../projects/js-packages/webpack-config/README.md) (more information on setup [in the README.md](../projects/js-packages/webpack-config/README.md)), note that your build-production command should set `NODE_ENV=production` and `BABEL_ENV=production`.
* If you're moving an admin dashboard from Webpack onto the wp-build (esbuild) pipeline, follow the [wp-build porting checklist](wp-build-porting-checklist.md).
* If you run into problems with Composer not recognizing the local git branch as being the right version, try setting `COMPOSER_ROOT_VERSION=dev-trunk` in the environment.
* When building for the mirror repos, note that `COMPOSER_MIRROR_PATH_REPOS=1` will be set in the environment and the list of repositories in `composer.json` may be altered.
This is not normally done in development environments, even with `jetpack build --production`.
Expand Down
Loading
Loading