You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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?
The text was updated successfully, but these errors were encountered: