Support for Monorepo Task Runners (Nx, Turbo, Rush) in Corepack
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 3.8k
- Forks
- 279
- Avg merge
- 1h 47m
- Merged PRs (30d)
- 2
Description
First of all, thank you for the great work on Corepack! It has made managing package managers across projects much more seamless, reducing the need for global installations and ensuring consistency across environments.
Building on this idea, it would be great to extend Corepack’s approach to monorepo task runners like Nx, Turborepo, and Rush. These tools are widely used in modern JavaScript/TypeScript monorepos to manage tasks like builds, tests, and linting efficiently. However, they currently require explicit global installs or workarounds like prefixing nx with e.g. npx nx ... or global installs with the risk of using a wrong version.
By providing a way to manage these tools similarly to package managers, developers could run nx, turbo, or rush directly without worrying about global installations, making monorepo workflows even smoother.
Would this be something worth exploring?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by reviewing Corepack’s existing package-manager support, then define how Nx, Turborepo, and Rush would be discovered, versioned, and invoked. Done requires an agreed scope and corresponding behavior for the requested monorepo task runners.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs, typescript
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100