Skip to content

feat: run commands in a directory with --dir - #911

Closed
Aschenbath wants to merge 1 commit into
nodejs:mainfrom
Aschenbath:feat/dir-option-677
Closed

Aschenbath wants to merge 1 commit into
nodejs:mainfrom
Aschenbath:feat/dir-option-677

Conversation

@Aschenbath

Copy link
Copy Markdown

Add corepack --dir <path> <command> ... to run Corepack utility commands and package managers from another directory. Support relative/absolute paths and --dir=path, load the target project's configuration, and forward arguments after the package manager name to that manager.

Use a Clipanion proxy command to change the working directory before dispatch, report invalid directories as usage errors, and keep leading options in the Corepack CLI parser so paths containing @ work. Document the syntax and add 12 CLI regressions, including a real pnpm subprocess that verifies both its working directory and forwarding of pnpm's own --dir option.

Validation on Node.js 24.20.0:

  • Build: passed.
  • Full Vitest suite with NOCK_ENV=replay: 9 files passed; 183 tests passed and 1 existing expected failure.
  • tsc --noEmit: passed.
  • ESLint with --max-warnings=0: passed.

Local test setup isolates inherited proxy settings from CLI fixtures while retaining access for the live npm-key check. Compilation caches were disabled to accommodate the small temporary filesystem. No tests were skipped or modified for these environment adjustments.

Closes #677

@aduh95

aduh95 commented Oct 20, 2026

Copy link
Copy Markdown
Contributor

This account has opened more than 10 PRs in the last 24 hours. This looks like bot activity, and will result in a ban if the behavior continues.

@aduh95 aduh95 closed this Oct 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

--dir option

2 participants