{"version":"2.1.323","anchor":"plugin-install-no-longer-routes-plugin-at-marketplace-to-npm-in","canonical_anchor":"plugin-install-no-longer-routes-plugin-at-marketplace-to-npm-in","heading":"Installing plugin@marketplace now always uses the marketplace","tier":"notice","area":"Plugins","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/plugin-install-no-longer-routes-plugin-at-marketplace-to-npm-in","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Installing `plugin@marketplace` now always uses the marketplace\n\nA plugin install written as `plugin@marketplace` now goes to the marketplace, even when it also looks like an npm package name\n\n**Unclear.** It is not stated whether plugins can still be installed from npm in some other way.\n\n**What**\n\nPlugins add commands and features to Claude Code. A marketplace is a catalogue that plugins are installed from. When you install a plugin written as `plugin@marketplace`, Claude Code now looks it up in that marketplace. Before, a name that could also be read as an npm package name was installed from npm, the public JavaScript package registry.\n\n**Why**\n\nPlugin names that resemble npm package names now resolve to the marketplace you named instead of being fetched from npm.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}