Skip to content

Tags: ChromeDevTools/devtools-protocol

Tags

v0.0.1617982

Toggle v0.0.1617982's commit message
Roll protocol to r1617982

v0.0.1617013

Toggle v0.0.1617013's commit message
Roll protocol to r1617013

v0.0.1616338

Toggle v0.0.1616338's commit message
Roll protocol to r1616338

v0.0.1615727

Toggle v0.0.1615727's commit message
Roll protocol to r1615727

v0.0.1612613

Toggle v0.0.1612613's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
chore: update deps and Node version (#349)

v0.0.1611976

Toggle v0.0.1611976's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
chore: work around Node.js 22 / npm issue (#352)

Running `npm install -g npm@latest` on Node.js 22.22.2 (which bundles npm 10.9.7) fails with `MODULE_NOT_FOUND: promise-retry`. This happens because npm 11.12.0 removed `promise-retry` from its bundle (in favor of `@gar/promise-retry`). During the self-upgrade, the reify step deletes `promise-retry` from disk, and then the still-running 10.x process hits a lazy `require('promise-retry')` in `_linkBins` and blows up.

The root cause has already been fixed upstream (npm/cli#9152) and released on npm 10.9.8.

However, we can avoid the problem altogether by removing the `npm install -g@latest` step. It was initially added because it was needed for Trusted Publishing at the time, but nowadays the bundled npm is modern enough that we don’t need to force the latest version anymore.

v0.0.1609665

Toggle v0.0.1609665's commit message
Roll protocol to r1609665

v0.0.1608973

Toggle v0.0.1608973's commit message
Roll protocol to r1608973

v0.0.1604597

Toggle v0.0.1604597's commit message
Roll protocol to r1604597

v0.0.1603894

Toggle v0.0.1603894's commit message
Roll protocol to r1603894