Verify the package name
DSH Plugin Hub syncs plugins from the npm Registry. The package name used during installation must exactly match the published npm name, including the scope (e.g. @author/plugin-name).
Common mistakes include: extra spaces, missing scope prefix, case mismatches. npm package names are all lowercase.
# Check if the package exists on npm
npm view @author/plugin-nameEnsure the DSH manifest exists
Every DSH plugin's package.json must include the dsh.bundle field pointing to a Cordis patch file. Packages missing this field are rejected by the Hub.
{
"name": "my-plugin",
"version": "1.0.0",
"dsh": {
"bundle": {
"patch": "./cordis.patch.yml"
}
}
}Version must be exact SemVer
The version field in package.json must be an exact semantic version (e.g. 1.2.3) — no range prefixes (^, ~) or tags.
Use dsh-hub validate to check all format issues before publishing:
dsh-hub validate my-pluginCheck the Cordis patch file
The patch file path is relative to package.json. Make sure the file exists, the YAML syntax is valid, and it contains at least one valid entry.
dsh-hub validate checks that entry IDs in the patch file match the entryIds declared in hub metadata.
Network issues
If the npm Registry is temporarily unreachable, the Hub retries automatically. Rejected packages are rechecked after one day. You can also manually submit a package name on the plugins page to speed up syncing.