Skip to content

Add Wirepeek to DevTools Extensions > Workflow - #196

Open
SYNCRoSoft wants to merge 1 commit into
ChromeDevTools:masterfrom
SYNCRoSoft:SYNCRoSoft-patch-2
Open

SYNCRoSoft wants to merge 1 commit into
ChromeDevTools:masterfrom
SYNCRoSoft:SYNCRoSoft-patch-2

Conversation

@SYNCRoSoft

Copy link
Copy Markdown

Supersedes #195 - same change, re-submitted so the commit is authored under the email my Google CLA is signed with (the first attempt used my GitHub noreply address, which the CLA bot can't match). I'll close #195.

Adds Wirepeek to DevTools Extensions > Workflow, at the bottom of the section per contributing.md.

Why it belongs here: it's a DevTools panel for traffic the Network tab shows but doesn't decode. WebSocket frames arrive on the wire as 42["event",{...}] - Engine.IO packet type 4 wrapping Socket.IO type 2 - with a bare 2 heartbeat mixed into application traffic, and binary payloads shown as an opaque blob. Wirepeek resolves the framing into event names and a JSON tree, and unwraps nested base64/gzip, MessagePack, CBOR and Thrift. It hooks WebSocket.prototype in the page's main world at document_start, so it captures the handshake and survives reloads - which the Network tab cannot when DevTools is opened after the connection.

Read-only, no account, no backend, one permission (storage). Free.

Disclosure: I'm the author. Published to the Chrome Web Store on 2 July 2026, well past the two-week guideline in contributing.md, and I use it daily on my own real-time work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant