Version Packages - #167
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
July 29, 2026 19:24
68834e9 to
4555556
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
July 29, 2026 19:29
4555556 to
7f92577
Compare
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@jantimon/web-performance-debugger@1.1.0
Minor Changes
#166
6e84b40- Clearer errors and a tidierquery spanscontract.runexport now gets a message naming the module and the one-line fix (export async function run(ctx) { ... }), instead of the placeholder'run' / 'run' export.WPD_DEBUG=1: the message always prints, and the full stack follows when the env is set. The one-line message trails the(set WPD_DEBUG=1 ...)hint so a caller reading only the last stderr line still sees the real error.query get <id>on a missing id points atquery events.query span'sforced[]read-sites move from theat: "file:line:col"string to structured{ source, line, column }, matchingquery blame --forced.query spansrows gain a compactframeFloor: { floorMs, multiple }when the wall is frame-floor dominated, so a consumer reads flooring off the overview instead of recomputing it.#168
21b14bd- React framework addon, opt-out via--framework off|auto(defaultauto):Span.addons.react.--target node): react-dom self-time rolled onto the stable server-phase anchors. React 19 production resolves them; React 18 production is mangled, so the fact is honestly absent.--deepdev builds (Span.addons["react-dev"]), classified from theTimeStampevents wpd already stores. A production browser build emits none, so this is absent there.--framework offruns zero addon code and leaves the recording unchanged. All React logic lives behind one registry interface the core never imports through; addons only read what the capture recorded.query spanshows a labeledReact (addon)block;--format jsonadds anaddonsobject. New public types:ReactFacts,ReactDevFacts,SpanAddons,FrameworkMode.