Repository navigation
docs: add Solid 2.0 server rendering fixes to the impact page - #746
Merged
Merged
Conversation
AlexanderKaran
approved these changes
Nov 3, 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.
Adds a "Faster Solid 2.0 server rendering" section to the impact page. It lists three upstream changes found while adding Solid 2.0 to the tracker (#709), all merged and released:
2.0.0-next.43).2.0.0-rc.20).2.0.0-rc.20).The numbers come from each PR's own measurements and from the #709 CI runs before and after the upgrade (SSR load from 170 to 280 req/s with one connection).
Verified with
pnpm buildinpackages/docsandprettier --checkon the page.Checklist
starter-*package, ensure that the deps, and file content matches the output of the metaframeworks recommended starter/default project🤖 Generated with Claude Code