bun install: error: No version matching "99.0.0" found for specifier "is-number" (but package exists)

error: No version matching "99.0.0" found for specifier "is-number" (but package exists) means Bun found the package on the registry, but no published version satisfies the version or range in package.json. The suffix (but package exists) tells you the name is right and only the version is wrong. List the real versions with npm view is-number versions and fix the entry, or run bun add is-number@latest.

Reproduce it

cat > package.json <<'EOF2'
{ "name": "app", "version": "1.0.0", "dependencies": { "is-number": "99.0.0" } }
EOF2
npx --yes bun@1 install 2>&1 | grep '^error'
exit "${PIPESTATUS[0]}"

error: No version matching "99.0.0" found for specifier "is-number" (but package exists)
error: is-number@99.0.0 failed to resolve

Bun prints a second line, error: is-number@99.0.0 failed to resolve, naming the dependency that stopped the install.

Fix

cat > package.json <<'EOF2'
{ "name": "app", "version": "1.0.0", "dependencies": { "is-number": "7.0.0" } }
EOF2
npx --yes bun@1 install >/dev/null 2>&1
node -p "require('is-number/package.json').version"

7.0.0

When the package name itself does not exist, the message has no (but package exists) suffix and the registry answers 404: check the spelling or the scope.