본문으로 건너뛰기
버전: 9.x

pnpm CLI

npm과의 차이점​

npm과 달리 pnpm은 모든 옵션의 유효성을 검사합니다. For example, pnpm install --target_arch x64 will fail as --target_arch is not a valid option for pnpm install.

However, some dependencies may use the npm_config_ environment variable, which is populated from the CLI options. 이러한 경우, 아래와 같은 옵션이 있습니다:

  1. explicitly set the env variable: npm_config_target_arch=x64 pnpm install
  2. force the unknown option with --config.: pnpm install --config.target_arch=x64

옵션​

-C <path>, --dir <path>​

Run as if pnpm was started in <path> instead of the current working directory.

-w, --workspace-root​

Run as if pnpm was started in the root of the workspace instead of the current working directory.

Commands​

자세한 내용은 각각의 CLI commands 문서를 참고하십시오. 다음 목록은 npm 커맨드와의 간단한 비교입니다.

npmpnpm
npm installpnpm install
npm i <pkg>pnpm add <pkg>
npm run <cmd>pnpm <cmd>

When an unknown command is used, pnpm will search for a script with the given name, so pnpm run lint is the same as pnpm lint. If there is no script with the specified name, then pnpm will execute the command as a shell script, so you can do things like pnpm eslint (see pnpm exec).

Environment variables​

Some environment variables that are not pnpm related might change the behaviour of pnpm:

These environment variables may influence what directories pnpm will use for storing global information:

  • XDG_CACHE_HOME
  • XDG_CONFIG_HOME
  • XDG_DATA_HOME
  • XDG_STATE_HOME

You can search the docs to find the settings that leverage these environment variables.