{"version":"2.1.323","anchor":"plugin-install-npm-registry-and-registry-support-removed","canonical_anchor":"plugin-install-npm-registry-and-registry-support-removed","heading":"Plugin install no longer accepts npm packages or the --registry option","tier":"notice","area":"Plugins","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/plugin-install-npm-registry-and-registry-support-removed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Plugin install no longer accepts npm packages or the `--registry` option\n\nThe plugin install command no longer handles `@npm` specs or the `--registry` option, and it has new failure codes\n\n**Unclear.** Whether installing plugins from npm is still possible some other way in this release is not clear.\n\n**What**\n\nPlugins are add-on packages for Claude Code. The plugin install command no longer handles these:\n\n- `<package>@npm` specs, which installed a plugin from the npm package registry\n\n- the `--registry <url>` option, which chose a different npm registry for such an install\n\n- the check that the `--registry` value is an http or https address\n\nInstall can also now stop with a new failure code, `engine_range`, and can report a failure code of `builtin` or `directory_loaded`.\n\n**Why**\n\nIf you installed plugins from npm, or pointed install at your own npm registry with `--registry`, that no longer works through this install command.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: yes"}