rtk-ai/rtk

Add `pnpm nx` command patterns for Nx monorepos

Open

#444 opened on Mar 9, 2026

View on GitHub
 (1 comment) (1 reaction) (0 assignees)Rust (2,914 forks)batch import
area:clieffort-mediumenhancementfilter-qualityhelp wantedpriority:medium

Repository metrics

Stars
 (48,085 stars)
PR merge metrics
 (Avg merge 11d 1h) (45 merged PRs in 30d)

Description

Problem

pnpm nx * commands are not covered by RTK's rewrite/compression patterns, causing them to pass through uncompressed. In our monorepo (Nx-managed, 20+ projects), we observed 313 pnpm nx * passthrough invocations in a single audit window — making this the largest single category of uncompressed output.

Related Issues

  • #122 — pnpm + glab integration (P3)
  • #259 — pnpm --filter support (PR #270 open)
  • #294 — pnpm exec / script dispatch

These all point to the same gap: pnpm as a command prefix is not systematically handled.

High-Impact Patterns

Command Frequency Notes
pnpm nx run <project>:<target> ~180 Build, typecheck, lint, test
pnpm nx show project <name> ~60 Project details (large JSON output)
pnpm nx graph ~30 Dependency graph
pnpm nx affected ~25 CI/change detection
pnpm nx run-many ~18 Batch operations

Suggested Approach

Add pnpm nx as a recognized command prefix in the rewrite rules, delegating to existing patterns where the underlying command is already supported (e.g., pnpm nx run -> build output compression).

Environment

  • RTK v0.27.2
  • pnpm v9.x
  • Nx 20.x monorepo

Contributor guide

Research direction
Identify where command prefixes are defined in the codebase and add 'pnpm nx' patterns following existing examples like 'pnpm run' or 'npm run'.
Tech stack
rust
Domain
cli
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
RustGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75