@percy/cli installation failing with npm

What to do

• Check whether you use Percy Percy. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.

  Anything that failed between 2026-09-24 23:42 UTC and 2026-09-24 23:42 UTC may need a replay.

• Subscribe to Percy's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=percy works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Percy 1

1. resolvedSep 24, 2026, 11:42 PM UTC

   Status: Fix released with percy/cli v1.32.11 Since 20:48 UTC on September 24, npm install @percy/cli fails with: npm ERR! code EUNSUPPORTEDPROTOCOL npm ERR! Unsupported URL Type "patch:": patch:got@npm%3A11.8.2#... With npm 10 and later, the install can fail with no error message. Cause: A third-party package that the Percy CLI depends on, @yarnpkg/core, published version 4.9.2 with a dependency format that npm can't install. Percy's services are not affected; only new CLI installs are. Fix: We have released a patch version of percy/cli v1.32.11 and now @latest should install correctly Workaround (for earlier percy cli versions if pinned): Add this to your project's root package.json: "overrides": { "@yarnpkg/core": "4.9.1" }

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.