refactor(preact): Drop preact-ssr-prepass
in favor of renderToStringAsync
#11464
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.
Changes
Closes #9733, alternative solution to #9733 (comment)
preact-ssr-prepass
to instead utilizerenderToStringAsync
frompreact-render-to-string
, which has surpassed it as the recommended tool, see chore: Update readme for suspense rendering preactjs/preact-render-to-string#338Testing
Existing tests should cover. Different implementation, but same intended result.
Docs
Users shouldn't need to know the method of rendering changed.
Additional Context
~6.3.1
, but rtsAsync is only available in6.4.0
and newer. I couldn't replicate the linked bug in newer versions so I imagine we fixed it at some point.preact-ssr-prepass
was our recommended solution but we have dropped references to it since. It certainly still works, but isn't what we'd recommend and issues might go somewhat unnoticed unfortunately -- small team, too many repos to juggle as it is.