{"version":"2.1.275","anchor":"adding-a-marketplace-by-link-now-needs-an-explicit-confirm-s","canonical_anchor":"new-plugin-install-from-source-and-npm-aware-marketplace-fl","heading":"Marketplace add-by-link now requires confirmation, plus new install routing","tier":"use","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/adding-a-marketplace-by-link-now-needs-an-explicit-confirm-s","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### Marketplace add-by-link now requires confirmation, plus new install routing\n\nAdding a plugin marketplace from a link now shows a confirmation step, with new install-from-source and npm-aware install flows\n\n**What**\n\n- Adding a marketplace from a link or URL, whether via `\/plugin marketplace add <path\/url>` or by installing a plugin from a link, now carries a `confirmAdd` payload. The add-marketplace screen automatically shows a confirmation step when this hasn't been set yet but a link-based source was provided.\n\n- A new `install-from-source` action routes to the add-marketplace screen with plugin and link-origin details for this confirmation step.\n\n- A new `usage-error` fallback routes back to the plugin menu instead of failing silently.\n\n- Installing now short-circuits to an npm-install path when the target parses as a `plugin@npm` spec.\n\n**Why**\n\nThis adds a safety check before trusting and adding a marketplace source from an arbitrary link, and cleans up how installs from different kinds of sources (links, npm packages, usage errors) are routed.\n\n- Area: Plugins\n- Names: `\/plugin marketplace add`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 2\/5"}