Deploy with pnpm
Use the package manager your project declares.
Select the project directory
For Node projects, an exact packageManager: pnpm@major.minor.patch or pnpm-lock.yaml selects pnpm. An explicit npm declaration wins over a leftover pnpm lockfile. Select the workspace root when it owns the lockfile, workspace settings and scripts. Bun projects use the Bun runtime.
{
"packageManager": "pnpm@11.19.0",
"scripts": { "build": "your-build-command", "start": "node dist/main.js" }
}Prepare pnpm explicitly
Portal install/update does not install pnpm. An owner can install it explicitly in Setup or prepare it over SSH. Portal supports installed pnpm 8–12 and checks for an exact version match when pinned. pnpm 11 requires Node 22.13 or newer. Deployment never downloads or switches the package manager. Install, build, startup and rollback use the selected manager and release Node major.
Fix the source, then retry
A frozen pnpm install includes build dependencies and stops when package.json and pnpm-lock.yaml disagree. Run pnpm install in your development checkout, review dependency changes, run the app checks and commit both files. Review pnpm-workspace.yaml build-script approvals yourself. Portal does not bypass peer conflicts or rewrite the synced source.