Compile blocks under assets/build/blocks/

[pratik-londhe4]

Description

Block source files under src/blocks/ weren't being compiled by the theme's build. This PR adds a dedicated build step that compiles them to assets/build/blocks/, matching the pattern in features-plugin-skeleton.

Technical Details

The theme's custom webpack.config.js only declares entries for src/css/ and src/js/{frontend,admin,editor}/ — src/blocks/ was not in any entry list. The reason blocks appeared to be built was that wp-scripts' inherited CopyPlugin was silently copying block.json / render.php from src/blocks/ into assets/build/js/blocks/. No edit.js / view.js / index.js were being compiled, and no *.asset.php was being emitted alongside.

The fix mirrors the plugin skeleton:

Checklist

• Add build:blocks npm script using wp-scripts' default config + --webpack-src-dir / --output-path
• Restructure build:dev and build:prod to fan out to *:js + :blocks
• Filter CopyPlugin out of inherited webpack plugins to stop duplicating block files into assets/build/js/blocks/
• Verify compiled output under assets/build/blocks/example-block-*/
• Verify assets/build/js/blocks/ no longer exists after a clean build

Screenshots

To-do

Fixes/Covers issue

Fixes #

[Copilot]

Pull request overview

This PR updates the theme’s build pipeline so block sources under src/blocks/ are compiled into assets/build/blocks/, and prevents @wordpress/scripts’ inherited copy behavior from duplicating block files into the JS build output.

Changes:

• Add a dedicated build:blocks script and fan build:dev / build:prod out into *:js + build:blocks.
• Filter out the inherited CopyPlugin from the theme’s extended webpack config to avoid copying block files into assets/build/js/blocks/.
• Update the npm lockfile to reflect dependency graph changes.

Reviewed changes

Copilot reviewed 2 out of 3 changed files in this pull request and generated 1 comment.

File	Description
webpack.config.js	Filters inherited webpack plugins to remove the wp-scripts CopyPlugin and avoid redundant block file copying into the JS output dir.
package.json	Introduces build:blocks and restructures build scripts to run both JS and block builds.
package-lock.json	Updates lockfile dependency metadata (currently inconsistent with package.json).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[aryanjasala]

build:blocks runs wp-scripts build (production mode) and is reused by both build:dev and build:prod. So a build:dev produces minified, source-map-less block output while the rest of the dev build is in development mode. Consider a dev block variant (wp-scripts start --no-watch …) so dev parity holds.

Also note npm start (--hot) doesn't call this at all, so blocks aren't compiled during HMR — and CleanBuildPlugin wipes assets/build on start, so there's no stale copy either.