setup-pm

You configure a default package manager by applying settings across local project config, package.json fields, and lockfiles to select pnpm, bun, yarn, or npm. This establishes a consistent tooling preference for your project environment.

The detection priority for selecting a package manager follows a strict fallback order: environment variables first, then project config, package.json fields, lockfiles, global user config, and finally a default fallback. This structured priority resolves conflicts when multiple lockfiles exist.

You set up consistent package manager tooling for a multi-repo team by configuring global user settings and project-level lockfile indicators to enforce a unified choice. This guarantees synchronized behavior across CI, local development, and deployment pipelines.

Yes, package manager configuration supports global user settings and environment variables. It applies preferences by checking environment variables and global config as part of its detection priority to determine whether to use pnpm, bun, yarn, or npm.

The best way to switch to pnpm is to update your project configuration and lockfile indicators to target pnpm. The configuration process uses these explicit settings to override old yarn cues and enforce the newly chosen package manager across your environment.