Skip to content

Conversation

fritzy
Copy link
Contributor

@fritzy fritzy commented Oct 13, 2021

npm commands that have workspaces specified can now additionally include the root with --include-workspace-root

For example, npm docs --workspaces --include-workspace-root will open docs links for the root package as well as each workspace, where as npm docs --workspaces only opens docs links for the workspaces.

npm commands can now filter out the application of workspaces entirely with --no-workspaces.

Specifying one, many, or all workspaces as well as --no-workspaces will result in an error.

@fritzy fritzy requested a review from a team as a code owner October 13, 2021 18:23
@wraithgar wraithgar changed the base branch from latest to release-next October 13, 2021 19:12
@nlf nlf force-pushed the fritzy/workspace-root branch from b6cc3ff to f879c10 Compare October 14, 2021 21:27
…spaces

Adds a new config item that includes the workspace root. This also changes
--workspaces to a trinary, so that setting it to false will explicitly exclude
workspaces altogether.

PR-URL: #3890
Credit: @fritzy
Close: #3890
Reviewed-by: @wraithgar
@nlf nlf force-pushed the fritzy/workspace-root branch from f879c10 to 24273a8 Compare October 14, 2021 21:41
@nlf nlf merged commit 24273a8 into release-next Oct 14, 2021
@nlf nlf mentioned this pull request Oct 14, 2021
@nlf nlf deleted the fritzy/workspace-root branch March 28, 2022 17:02
@vidal7
Copy link

vidal7 commented Jan 30, 2024

Hello. How does --no-workspaces works? I don't find any documentation about that? I thought that I can use this switch to call a root script from a package location.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants