-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Tools: Enforce the same order of fields in package.json
files
#66239
base: trunk
Are you sure you want to change the base?
Conversation
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. |
Size Change: 0 B Total Size: 1.77 MB ℹ️ View Unchanged
|
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.
Nice, this looks good. Let's land against trunk
after #65681 lands.
d10c7d6
to
770ab08
Compare
this should be done another way
Co-authored-by: Jon Surrell <[email protected]>
442fea4
to
e5eab2e
Compare
What?
Depends on:
There were new properties introduced in
package.json
files that are located in random order inpackage.json
files:exports
wpScript
wpScriptModuleExports
sideEffects
Why?
It's easier to have consitent order of fields when maintaining nearly 100 npm packages.
How?
Extend the config for
prefer-property-order
rule in@wordpress/npm-package-json-lint-config
.