WordPress build tooling is about to change.
WordPress build tooling is about to change. Not in a disruptive way — most developers who use @wordpress/scripts today will not need to change anything when the transition happens. But the underlying engine, the philosophy, and the developer experience are all shifting, and the window to influence that direction is open right now.
@wordpress/build is the tool driving that shift. It replaces the webpack and Babel pipeline with a significantly faster build engine, auto-generates PHP registration files from package.json conventions, and handles scripts, script modules, and styles in one pass.
It works through convention-based folder discovery: a packages/ directory for JavaScript packages, and a routes/ directory for admin page routes — each auto-discovered with no configuration. Gutenberg already uses it to build all of its 100+ packages.
The long-term plan is for it to become the engine underneath @wordpress/scripts, so every plugin developer benefits from the same tooling — without changing their workflow.
@wordpress/build is not ready for every use case yet. In particular, a plugin registering blocks — a common entry point for WordPress plugin developers — still has gaps that require manual workarounds.