{"version":"2.1.275","anchor":"plugin-loading-splits-out-npm-sourced-plugins-from-marketpla","canonical_anchor":"plugin-loading-splits-out-npm-sourced-plugins-from-marketpla","heading":"Plugin loading splits out npm-sourced plugins from marketplace catalog flow","tier":"internal","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/plugin-loading-splits-out-npm-sourced-plugins-from-marketpla","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### Plugin loading splits out npm-sourced plugins from marketplace catalog flow\n\nPlugins installed from npm are now resolved through a separate code path from marketplace plugins\n\n**What**\n\nWhen Claude Code figures out which plugins are enabled, plugins whose source is the special \"npm\" pseudo-marketplace are no longer processed through the normal marketplace-catalog lookup. Instead they are resolved through a dedicated path built specifically for npm-sourced plugins.\n\n**Why**\n\nThis separates the handling of plugins installed via npm from plugins installed via a marketplace catalog, which should make npm-based plugin installs more reliable since they no longer have to go through machinery meant for marketplace catalogs.\n\n- Area: Plugins\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}