{"version":"2.1.247","anchor":"finished-npm-installs-for-plugins-are-detected-instead-of-re","canonical_anchor":"finished-npm-installs-for-plugins-are-detected-instead-of-re","heading":"Finished npm installs for plugins are detected instead of repeated","tier":"notice","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/finished-npm-installs-for-plugins-are-detected-instead-of-re","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Finished npm installs for plugins are detected instead of repeated\n\nPlugin npm installs that already finished are recognised and skipped instead of run again.\n\n**What**\n\nnpm dependency installs now record `node_modules\/.package-lock.json` as a completion marker, so an install that already finished can be recognised rather than run again.\n\n**Details**\n\n- Two lookups were added alongside it: a list of lockfiles and a map from lockfile to its completion marker.\n\n**Evidence**\n\n`node_modules\/.package-lock.json`\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}