Repository navigation
Move the trace zip reader from backend into trace - #506
Merged
Merged
Conversation
The planned trace query MCP server (#493) needs to parse trace zips, and depending on backend for that would pull Fastify, the dashboard bundle and the rerun spawner into its install. The reader imports only shared and trace, so it moves to trace, which now owns the format in both directions. readTraceZip moves with parseTraceZip because trace already does the matching disk write and both backend and the MCP package read from disk. The reader stays out of trace's index, so core and the adapters never inline it. No behaviour change: backend imports it by subpath. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Oct 29, 2026
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.
What & why
Part of #494 (the hosted trace player parses zips in the browser) and prepares #493.
Moves the trace zip reader (
parseTraceZip,readTraceZipand thetrace-reader-*siblings) frompackages/backendintopackages/trace, which now owns the trace format in both directions. Two consumers need to parse a trace zip without the backend: the hosted trace player, since the app cannot import the backend, and the planned trace query MCP server (#493), which would otherwise pull Fastify, the dashboard bundle and the rerun spawner into its install.Type of change
Packages touched
shared(types and contracts)core(framework-agnostic capture/reporting)elements(published element/snapshot API —@wdio/elements)service(WebdriverIO adapter)nightwatch-devtools(Nightwatch adapter)selenium-devtools(Selenium adapter)selenium-devtools-py(Selenium Python adapter)backend(server)app(UI)script(page-injected runtime)trace(Trace mode)Capability matrix
packages/conformance/src/features.tsupdated, and tables regenerated withpnpm docs:capabilities, if this adds or changes user-facing behaviourNot needed: no behaviour change.
Notes for reviewers
sharedandtrace, so it belongs intrace. It stays out oftrace's index, socoreand the adapters never inline it; the backend imports it by subpath.Screenshots / recordings
Not applicable: no UI change.
🤖 Generated with Claude Code