-
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
Conversation
Size Change: 0 B Total Size: 1.84 MB ℹ️ View Unchanged
|
Flaky tests detected in c311cc9. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/12580277890
|
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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have not tested done manual testing.
The changes and documentation updates look correct.
I included testing instructions in the PR's description that I used to validate that the changes work as expected. |
* Scripts: Recommend passing JS entry points with paths * Add changelog entries * Improve the code documentation * Improve the code documentation * Improve documentation around the source path Co-authored-by: gziolo <[email protected]> Co-authored-by: sirreal <[email protected]>
* Scripts: Recommend passing JS entry points with paths * Add changelog entries * Improve the code documentation * Improve the code documentation * Improve documentation around the source path Co-authored-by: gziolo <[email protected]> Co-authored-by: sirreal <[email protected]>
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
Create a new
my-plugin
folder:mkdir my-plugin cd my-plugin
Create a
package.json
file:Create two JavaScript files in the
my-plugin
subfolder:entry-one.js
entry-two.js
Run the build
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:Ensure that two files were bundled in the
dist
folder: