ERR_PNPM_IGNORED_BUILDS Ignored build scripts How to fix it.

What it means

Some packages unpack a ready-made program in an install script. esbuild and sharp are two. From pnpm 11, a script like that does not run unless you approve it. Blocking it makes the package install and then fail to run. The message lists the packages that were blocked.

How to fix it

The log suggests pnpm approve-builds, but that command is interactive and cannot work on a build server. Current pnpm reads the approval from pnpm-workspace.yaml, not from package.json.

1. Create or open pnpm-workspace.yaml at the root of your project

   If there is no such file, create one.

2. List the packages the message named

   Use the allowBuilds setting, with each package set to true.

   pnpm-workspace.yaml

   allowBuilds:
     "esbuild": true
     "sharp": true

3. Commit it and deploy again

   A failed deploy never counts against your plan.

What Antideploy does

Antideploy recognises this failure. It adds allowBuilds for the packages the log names, in its own copy of your source, and tells you it did. It never edits your repository, so commit the file yourself to build the same way everywhere.