Registry failed to return tag "buffer" with Yarn 2 and 3

[lorisleiva]

A nested dependency uses the npm:buffer alias as a dependency without providing a version range which causes the SDK installation to fail on Yarn version 2 and 3 (See yarnpkg/berry#1816).

buffer@npm:buffer: Registry failed to return tag "buffer"

The dependency that uses that tag is https://github.com/Bundlr-Network/arbundles which is a dependency of https://github.com/Bundlr-Network/js-client

Dependency tree

• @bundlr-network/client (GitHub repo, package.json)
  • arbundles (GitHub repo, package.json)
    → Requires npm:buffer as a dependency

Steps to reproduce

For Yarn 3

mkdir js-next-yarn-3
cd js-next-yarn-3
yarn set version stable
yarn -v # <- 3.2.0
yarn add @metaplex-foundation/js-next # <- Error

For Yarn 2

mkdir js-next-yarn-2
cd js-next-yarn-2
yarn set version 2.x
yarn -v # <- 2.4.3
yarn add @metaplex-foundation/js-next # <- Error

Solution

We need to upgrade our @bundlr-network/client dependency to 0.8.0-rc1. (Checking with Josh first as it's not a stable version yet). 0.7.3.

Version 0.7.2 of @bundlr-network/client uses version 0.6.17-rc1 of arbundles which is requires the npm:buffer dependency.

Version 0.8.0-rc1 of @bundlr-network/client uses version 0.7.0-rc2 of arbundles which only requires the npm:buffer as a dev dependency and therefore solves this issue.

EDIT: Version 0.7.3 now also fixes this issue after talking to Josh.

[lorisleiva]

Fix released in version 0.7.3. 🚀

Cc @austbot (FYI)