Codex/node network devtools v2 - #64
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
zero-code CLI setup, capability-aware fallback, official DevTools support,
Session/HAR/Replay/Trace, and Legacy-only request mocking.
privacy-reviewed screenshots, 17 structured artifacts, five reproduction
harnesses, and a 51-file SHA-256 manifest.
package completes the HTTP/2 lifecycle on Node 22.22.3; Node 24.16/26.8
reproduce an upstream Inspector crash, so those and unverified future majors
now correctly advertise
http2=false.Manual acceptance evidence
--version,doctor, zero-code Native/Legacy, invalid Native + Mock, public replay dry/real, exact-target--openOpen the full 14-case report with expected/observed results and every evidence link
Evidence identity and validation
449d47db89109e826eb0e7e0584777365eac3f9bnode-network-devtools@2.0.0, 190 filese97dc360d2fcd5d141b13bca490f603b802dc7fe94f3b6a06a690c7a7f48e2acpull-request run 33154271318
and
push run 33154267596
both passed, including packed consumers, Native/Legacy protocol E2E,
Windows/macOS 20-round smoke, and the official Chromium frontend
The manual run used only loopback traffic and an isolated consumer installed
from the exact tarball. Local filesystem prefixes were redacted; protocol
methods, bodies, statuses, event counts, and lifecycle semantics were retained.