From 96d5104f7d3bde5d5d36ce4bc7b1e522421146ad Mon Sep 17 00:00:00 2001 From: Ruy Adorno Date: Wed, 9 Feb 2022 12:20:19 -0500 Subject: [PATCH] update phrase on workspace-aware commands --- accepted/0000-workspaces-auto-cwd-context.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/accepted/0000-workspaces-auto-cwd-context.md b/accepted/0000-workspaces-auto-cwd-context.md index a24a3f18b..e733c4681 100644 --- a/accepted/0000-workspaces-auto-cwd-context.md +++ b/accepted/0000-workspaces-auto-cwd-context.md @@ -12,7 +12,7 @@ Unfortunately that might not work as intended depending on the command, for exam ## Detailed Explanation -Now that we are landing support to **workspace-aware** commands (see: [#117](https://github.com/npm/rfcs/pull/117)) a potential fix to that mismatch between the expected user experience and the current behavior of the npm cli is to automatically switch the internal context to ensure that if the user is trying to run a command that already support the **workspaces configurations**. +Given that the cli currently support **workspace-aware** commands (via `--workspaces` and `--workspace` configs) a potential fix to that mismatch between the expected user experience and the current behavior of the npm cli is to automatically switch the internal context to ensure that if the user is trying to run a command that already support the **workspaces configurations**. ## Rationale and Alternatives