run-many does not recognize targets with a colon

[dlqqq]

Current Behavior

run-many does not recognize targets with a colon in the name, even when wrapped with escaped quotes like so:

% yarn nx run-many --target=\"build:prod\"

Expected Behavior

run-many should recognize targets wrapped in double quotes.

GitHub Repo

https://github.com/dlqqq/nx-colon-issue

Steps to Reproduce

1. Run nx run --target=build and run nx run --target=\"build:prod\".
2. Verify you see the following output:

% yarn nx run-many --target=build
yarn run v1.22.19
$ /workplace/dlq/nx-colon-issue/node_modules/.bin/nx run-many --target=build

    ✔  nx run test:build  [local cache]

 ——————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————

 >  NX   Successfully ran target build for project test (61ms)

   Nx read the output from the cache instead of running the command for 1 out of 1 tasks.

Done in 0.34s.
(jai)
(23-04-10 17:54:53) <0> [/workplace/dlq/nx-colon-issue]
dev-dsk-dlq-2b-55651109 % yarn nx run-many --target=\"build:prod\"
yarn run v1.22.19
$ /workplace/dlq/nx-colon-issue/node_modules/.bin/nx run-many '--target="build:prod"'
 >  NX   Successfully ran target "build:prod" for 0 projects (5ms)

Done in 0.28s.

Nx Report

>  NX   Report complete - copy this into the issue template

   Node : 18.13.0
   OS   : linux x64
   yarn : 1.22.19

   nx            : 15.9.2
   lerna         : 6.6.1
   @nrwl/cli     : 15.9.2
   @nrwl/devkit  : 15.9.2
   @nrwl/tao     : 15.9.2
   typescript    : 4.1.6

Failure Logs

No response

Additional Information

No response

[AgentEnder]

You can run this via nx run-many --target build:prod - the surrounding quotes aren't necessary with run-many, affected, or infix notation (e.g. nx build:prod project)

[github-actions]

This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context.