{"version":"2.1.275","anchor":"npm-sourced-plugin-marketplaces-added-several-other-sources","canonical_anchor":"npm-sourced-plugin-marketplaces-added-several-other-sources","heading":"npm-sourced plugin marketplaces added; several other sources reserved for future use","tier":"soon","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/npm-sourced-plugin-marketplaces-added-several-other-sources","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### npm-sourced plugin marketplaces added; several other sources reserved for future use\n\nPlugin marketplaces can now source plugins from npm; pip\/uv\/cargo\/github\/gh sources are reserved but not yet usable\n\n**What**\n\nPlugin marketplaces can now use `npm` as a real source, letting you install plugins from an npm registry using the form `<package>@npm`. Several other source names \u2014 pip, uv, cargo, github, and gh \u2014 are also now recognized as reserved names, but they are not yet available for actual use.\n\n**Why**\n\nThis gives plugin authors and users a working way to distribute and install plugins through npm today, while signaling that support for other package ecosystems is planned.\n\n- Area: Plugins\n- Names: `@npm`\n- Tier: Nothing to try yet\n- Useful: 4\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}