{"version":"2.1.287","anchor":"plugin-dependency-install-gains-an-extra-argument","canonical_anchor":"plugin-dependency-install-gains-an-extra-argument","heading":"Plugin dependency installs reworked, with a shared lockfile check","tier":"internal","area":"Plugins","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/plugin-dependency-install-gains-an-extra-argument","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Plugin dependency installs reworked, with a shared lockfile check\n\nThe step that installs a plugin's npm or bun packages takes an extra input and checks lockfiles through a shared check\n\n**Unclear.** It is not clear what the extra input changes about how plugin dependencies are installed.\n\n**What**\n\nSome plugins need packages installed with npm or bun, two tools that download JavaScript packages. The step that installs them now accepts an extra, optional input. Its check of the lockfile (the file that pins exact package versions) now goes through a shared check instead of a separate error written just for the `bun.lockb` file.\n\n**Why**\n\nIf you use plugins that come with npm or bun packages, this is the step that installs them, and that tells you when Claude Code skipped installing a plugin's dependencies. The messages you see there may differ.\n\n- Area: Plugins\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}