Bug
Fresh installs of pm2 currently fail:
$ npm i pm2
npm error code ETARGET
npm error notarget No matching version found for js-yaml@4.3.0.
Cause
pm2@7.0.2 and 7.0.3 pin the exact version "js-yaml": "4.3.0". That version is no longer available on the registry — npm view js-yaml@4.3.0 returns E404, and the newest published version is 4.2.0 (latest dist-tag). js-yaml 4.3.0/5.x appear to have been unpublished recently (the js-yaml repo has June issues referencing v5 releases that are gone from npm now).
7.0.1 (pinned to 4.1.1) still installs, but 4.1.1 is the release flagged by GHSA-h67p-54hq-rp68 that prompted the bump in #6122.
The development branch also pins 4.3.0, so the next release would ship broken too.
Fix
Repin to 4.2.0 (newest available, and the version the advisory called for). PR incoming.
Bug
Fresh installs of pm2 currently fail:
Cause
pm2@7.0.2and7.0.3pin the exact version"js-yaml": "4.3.0". That version is no longer available on the registry —npm view js-yaml@4.3.0returns E404, and the newest published version is4.2.0(latestdist-tag). js-yaml 4.3.0/5.x appear to have been unpublished recently (the js-yaml repo has June issues referencing v5 releases that are gone from npm now).7.0.1(pinned to4.1.1) still installs, but 4.1.1 is the release flagged by GHSA-h67p-54hq-rp68 that prompted the bump in #6122.The
developmentbranch also pins4.3.0, so the next release would ship broken too.Fix
Repin to
4.2.0(newest available, and the version the advisory called for). PR incoming.