{"version":"2.1.284","anchor":"plugin-dependencies-given-by-bare-name-now-resolve-to-the-ma","canonical_anchor":"plugin-dependencies-given-by-bare-name-now-resolve-to-the-ma","heading":"Plugin dependencies named without a marketplace now match your installed plugin","tier":"notice","area":"Plugins","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/plugin-dependencies-given-by-bare-name-now-resolve-to-the-ma","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### Plugin dependencies named without a marketplace now match your installed plugin\n\nA plugin dependency given by name alone is now satisfied by, and resolves to, the matching enabled plugin from a marketplace\n\n**Unclear.** It is not clear exactly how plugin names are rewritten into a consistent form before they are compared.\n\n**What**\n\nA plugin can list other plugins it depends on. A dependency can be written as a bare name, or with `@marketplace` added to say which marketplace it comes from.\n\nA dependency given as a bare name is now satisfied by an enabled plugin of that name from a marketplace, and Claude Code resolves it to that specific plugin. Before, a bare dependency was checked only by counting plugins with that name. Claude Code also now puts plugin names in a consistent form before comparing them, including when it reads `enabledPlugins`, the setting that turns plugins on or off. Before, `enabledPlugins` was matched on the exact name only.\n\n**Why**\n\nThis should stop false \"dependency not found\" errors for plugins that name their dependencies without a marketplace, when the plugin they need is installed and enabled.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}