Repository navigation
Version Packages (next) - #44
Open
github-actions[bot] wants to merge 1 commit into
Open
github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
5 times, most recently
from
November 4, 2026 05:01
8b329ee to
f529fc2
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
November 4, 2026 05:04
f529fc2 to
6ce0ef8
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.
mainis currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, runchangeset pre exitonmain.Releases
@solidjs/start-devtools@1.0.0-next.9
Minor Changes
d99ff2c: Add an Async panel that shows what the app is loading now, and how its async loads, waits and fallbacks went.
2b8a936: Add an Issues panel that lists the issues the Solid runtime reports, such as a signal read outside a tracking scope. Each one is an error, a warning or info.
52dc743: Add live state and store editing to the dev toolbar.
Signals and stores can now be inspected and edited live on-the-fly directly from the devtools:
Map, aSet, a typed array or a class instance are shown but not editable. An edit the app does not take is marked in the panel.ed9f773: Make the detail panes in the Ownership and Reactivity panels resizable. Drag the left edge of a pane, or focus it and press the left and right arrow keys. Each pane keeps its own width across reloads, and a double-click on the edge resets it.
c6402b7: The dock header has a button that copies one report of the whole session for an agent: the newest errors, the issues, the recent timeline actions, the flagged async records and the failed server calls.
588365e: Add a Timeline panel that lists what each user action re-ran, and why.
Patch Changes
368b4c9: The toolbar keeps the 200 newest errors, so an error thrown in a loop no longer grows the list without end.
212dad4: Errors thrown by browser extensions' scripts in the page are no longer listed as the app's errors.
fd65515: Show the body of server function calls that send files.
With
enableRichArguments()in@solidjs/web2.0.0-rc.20, a call whose arguments hold aFileorBlobsends multipart form data markedX-Server-Function-Format: 0. The panel read that body as a seroval stream and showed no body. It now shows the arguments in the seroval tree and the files in a form data table. Reports copied for an agent list both.