{"version":"2.1.287","anchor":"marketplace-and-plugin-install-error-codes-extended","canonical_anchor":"marketplace-and-plugin-install-error-codes-extended","heading":"Plugins report when their dependencies were not installed","tier":"notice","area":"Plugins","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/marketplace-and-plugin-install-error-codes-extended","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Plugins report when their dependencies were not installed\n\nPlugin installs gain new errors and warnings for dependencies that were not installed, screened or allowed, plus stricter marketplace source checks\n\n**Unclear.** Where the two dependency error codes are raised is not shown.\n\n**What**\n\nA plugin can depend on extra packages. Claude Code now has specific error codes and warnings for when those packages are not set up. It also tightens some checks on where a marketplace comes from. A marketplace is a catalog you install plugins from.\n\n- `dependencies_not_installed` and `dependencies_not_screened` are new error codes in the marketplace error list. Both are classed as `bad`.\n\n- Plugin warning hints gain two new cases, dependencies-refused and dependencies-not-installed. The warning explains that if the plugin needs those packages, parts of it may not work.\n\n- When a marketplace URL fails its format check, the failure is now labelled `manifest_invalid`.\n\n- The check for GitHub shorthand sources (the short `owner\/repo` way of naming a repository) now validates the repository part. Before, it checked the ref part, meaning the branch or tag.\n\n**Why**\n\nA plugin whose dependencies were skipped, refused or not checked can look installed but only partly work. These warnings tell you why, so you know to install or allow the missing packages instead of guessing what broke.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}