`pnpm --filter` command results in rtk usage output

[KuSh]

Always prefix commands with rtk. If RTK has a dedicated filter, it uses it. If not, it passes through unchanged. This means RTK is always safe to use.

Contrary to what rule says, it isn't safe for pnpm commands:

$ rtk pnpm --filter mymodule test **/*.spec.ts
error: unexpected argument '--filter' found

Usage: rtk pnpm [OPTIONS] <COMMAND>

For more information, try '--help'.

Why not pass everything unknown to the target?

[TechWizard9999]

I’m taking this one. I’ll make Version 10.28.2 (compiled to binary; bundled Node.js v22.19.0)
Usage: pnpm [command] [flags]
pnpm [ -h | --help | -v | --version ]

These are common pnpm commands used in various situations, use 'pnpm help -a' to list all commands

Manage your dependencies:
add Installs a package and any packages that it depends
on. By default, any new package is installed as a
prod dependency
i, install Install all dependencies for a project
ln, link Connect the local project to another one
rm, remove Removes packages from node_modules and from the
project's package.json
unlink Unlinks a package. Like yarn unlink but pnpm
re-installs the dependency after removing the
external link
up, update Updates packages to their latest version based on the
specified range

Review your dependencies:
audit Checks for known security issues with the installed
packages
ls, list Print all the versions of packages that are
installed, as well as their dependencies, in a
tree-structure
outdated Check for outdated packages
why Shows all packages that depend on the specified
package

Run your scripts:
create Create a project from a "create-" or "@foo/create-"
starter kit
dlx Fetches a package from the registry without
installing it as a dependency, hot loads it, and runs
whatever default command binary it exposes
exec Executes a shell command in scope of a project
run Runs a defined package script

Other:
c, config Manage the pnpm configuration files
init Create a package.json file
publish Publishes a package to the registry
self-update Updates pnpm to the latest version

Options:
-r, --recursive Run the command for each project in the workspace. accept flag-first invocations (like ) by routing unsupported forms to passthrough, with regression tests and changelog update, then open a focused PR.

@aeppling tagging for visibility.

[TechWizard9999]

I’m implementing this with exact scope: support flag-first calls such as No projects found in "/Users/stack/Documents/rtk" by passing through safely when pnpm args are not RTK-specialized subcommands. I’ll include regression tests and changelog update.

@aeppling tagging for review visibility.

[TechWizard9999]

Implemented and opened PR #681: #681

What I changed:

• switched Version 10.28.2 (compiled to binary; bundled Node.js v22.19.0)
  Usage: pnpm [command] [flags]
  pnpm [ -h | --help | -v | --version ]

These are common pnpm commands used in various situations, use 'pnpm help -a' to list all commands

Manage your dependencies:
add Installs a package and any packages that it depends
on. By default, any new package is installed as a
prod dependency
i, install Install all dependencies for a project
ln, link Connect the local project to another one
rm, remove Removes packages from node_modules and from the
project's package.json
unlink Unlinks a package. Like yarn unlink but pnpm
re-installs the dependency after removing the
external link
up, update Updates packages to their latest version based on the
specified range

Review your dependencies:
audit Checks for known security issues with the installed
packages
ls, list Print all the versions of packages that are
installed, as well as their dependencies, in a
tree-structure
outdated Check for outdated packages
why Shows all packages that depend on the specified
package

Run your scripts:
create Create a project from a "create-" or "@foo/create-"
starter kit
dlx Fetches a package from the registry without
installing it as a dependency, hot loads it, and runs
whatever default command binary it exposes
exec Executes a shell command in scope of a project
run Runs a defined package script

Other:
c, config Manage the pnpm configuration files
init Create a package.json file
publish Publishes a package to the registry
self-update Updates pnpm to the latest version

Options:
-r, --recursive Run the command for each project in the workspace. to raw-args parsing so flag-first invocations no longer fail clap parsing

• added routing for known optimized pnpm paths and passthrough for unsupported/flag-first forms
• added regression tests and changelog entry

Validation:

• cargo clippy: 0 errors, 2 warnings
  ═══════════════════════════════════════
  this else { if .. } block can be collapsed (2x)
  src/gh_cmd.rs:657:20
  src/git.rs:910:12
• ✓ cargo test: 952 passed, 3 ignored (1 suite, 0.74s)
• manual repro with No projects found in "/Users/stack/Documents/rtk" (now reaches pnpm)

@aeppling please review when convenient.