Troubleshooting
Fix a DSH rc dependency 404
A DSH rc dependency 404 usually means the requested package name or version is absent from the configured registry, not that retrying will repair it.
01
Capture the exact package request
Record the registry URL, package name, requested version, and lockfile entry from the 404 output before changing configuration.
- Check scope spelling
- Inspect the configured registry
- Compare the lockfile with upstream
02
Choose evidence-backed recovery
Use a published stable version, corrected registry, or upstream replacement only when the repository documents it. Never invent a package name from a plugin display name.
- Prefer current upstream instructions
- Remove stale lock entries carefully
- Keep the change reversible
Review sources
Sources help verify current facts. Their inclusion does not imply endorsement of this page.
DSH rc dependency 404 questions
What causes a DSH rc dependency 404?
The configured registry has nothing published under that name and version. The usual reasons are an unpublished release candidate, a misspelled scope, an internal mirror that never carried it, or a lockfile pinning a version that no longer exists.
Is a DSH rc dependency 404 a network problem?
Usually not. A 404 is a successful request with a negative answer, which is exactly why retrying does not help, whereas real network problems surface as timeouts or DNS errors instead.
How do I check what the registry actually has?
Query the registry for that package directly and list its published versions. Compare the result against the exact name and version in both the error output and your lockfile.
Should I pin a different version to get past it?
Only a version the repository documents as supported. Picking an arbitrary version that happens to resolve can install something incompatible with the plugin's current code.
Why do rc versions disappear from a registry?
Prerelease builds are routinely unpublished or superseded, and some registries prune them automatically. Depending on an rc means accepting that it can vanish, so prefer a stable release whenever one exists.