What?

• Part of Create Block: Streamline experience for working with multiple blocks and shared assets #68190.
• Alternative to WP Scripts: Automatically detect entry points for the default JS and CSS files #66466.

Improves listing entry points in the build commands: build and start from the @wordpress/scripts package. Using explicit entry points in the command becomes the recommended way to build the project that contains JavaScript code for UI plugins extending the editor in WordPress core.

Why?

Today, @wordpress/create-block is too optimized for the specific use case of developing a single block as a WordPress plugin. Things quickly get more complicated when a custom JavaScript is integrated to extend the block editor. In particular, extending the default webpack config included with @wordpress/scripts is way too complex. This is an attempt to address it by promoting an improved strategy for handling multiple JacaScript files as entry points.

How?

Testing Instructions

Create a new my-plugin folder:

mkdir my-plugin
cd my-plugin

Create a package.json file:

npm init

Create two JavaScript files in the my-plugin subfolder:

entry-one.js

console.log( 'entry one' );

entry-two.js

console.log( 'entry two' );

Run the build

../node_modules/.bin/wp-scripts build entry-one.js entry-two.js

Ensure that two files were bundled in the build folder:

Move two entry points to the test folder and run the command again with different params:

../node_modules/.bin/wp-scripts build entry-one.js entry-two.js --source-path=test --output-path=dist

Ensure that two files were bundled in the dist folder: