-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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.
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
Scripts: Recommend passing JS entry points with paths #68251
base: trunk
Are you sure you want to change the base?
Conversation
Size Change: 0 B Total Size: 1.84 MB ℹ️ View Unchanged
|
Flaky tests detected in 410bba4. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/12471391077
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.
To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
What?
Improves listing entry points in the build commands:
build
andstart
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