-
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
Use NPM workspaces #59933
Use NPM workspaces #59933
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. |
👋 Thanks for your first Pull Request and for helping build the future of Gutenberg and WordPress, @yusuke-omae! In case you missed it, we'd love to have you join us in our Slack community. If you want to learn more about WordPress development in general, check out the Core Handbook full of helpful information. |
234fc3c
to
7dd6499
Compare
7dd6499
to
0bcd744
Compare
@kevin940726, I see some Ci jobs failed. Do you remember what other changes were necessary to enable workspaces? |
I don't recall exactly the parts needed, but I also don't remember having to change so many lines in |
@yusuke-omae 👋 Thanks for starting on this. Work to migrate to npm workspaces was unintentionally duplicated in #65681. If you're interested in collaborating on it please help out there. |
What?
Enable npm workspaces.
Why?
npm workspace can detect incorrect management of monorepo.
This PR is a follow-up to #48950 and #53426.
How?
Testing Instructions
Testing Instructions for Keyboard
Screenshots or screencast