Use workspaces settings in package #7092
Conversation
With this change we can leverage npm's workspaces settings which will allow to achieve the following: 1 - running `npm install` from the root of the project will install all dependencies for all packages in any folder that is listed in the "packages" array. 2 - all dependencies with be placed in the main `node_modules` folder unless we need to keep some dependencies separated. For which case we can leverage the "nohoist" option.
davidecavaliere
requested review from
JavierGi,
ar2rsawseen and
kanwarujjaval
There was a problem hiding this comment.
Pull request overview
This PR adds npm workspaces configuration to the root package.json, enabling centralized dependency management across multiple packages within the monorepo. With this change, running npm install from the project root will automatically install dependencies for all workspace packages and place them in a shared node_modules folder.
Key Changes
- Adds workspaces configuration with glob patterns to identify package locations
- Configures paths for api utilities, plugins, UI tests, and bin utilities as workspace packages
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
package.json
Outdated
| "ui-test/*", | ||
| "bin/**/*" |
There was a problem hiding this comment.
The workspace pattern "bin/**/*" is overly broad and will cause issues. The bin directory does not contain any package.json files in its subdirectories. This pattern will not match any valid npm packages and should be removed from the workspaces configuration. If packages are added to bin in the future, this pattern can be reconsidered, but currently it serves no purpose and may cause confusion.
| "ui-test/*", | |
| "bin/**/*" | |
| "ui-test/*" |
Co-authored-by: Copilot <[email protected]>
Use workspaces settings in package
With this change we can leverage npm's workspaces settings which will
allow to achieve the following:
1 - running
npm installfrom the root of the project will install alldependencies for all packages in any folder that is listed in the "packages" array.
2 - all dependencies with be placed in the main
node_modulesfolderunless we need to keep some dependencies separated. For which case we
can leverage the "nohoist" option.