fix: follow-up formatting in print() for block-level elements#17699
Merged
Rich-Harris merged 1 commit intomainfrom Feb 13, 2026
Merged
fix: follow-up formatting in print() for block-level elements#17699Rich-Harris merged 1 commit intomainfrom
print() for block-level elements#17699Rich-Harris merged 1 commit intomainfrom
Conversation
🦋 Changeset detectedLatest commit: ef6d721 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Contributor
|
Merged
Rich-Harris
pushed a commit
that referenced
this pull request
Feb 13, 2026
This PR was opened by the [Changesets release](https://github.com/changesets/action) 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 ## svelte@5.51.0 ### Minor Changes - feat: Use `TrustedTypes` for HTML handling where supported ([#16271](#16271)) ### Patch Changes - fix: sanitize template-literal-special-characters in SSR attribute values ([#17692](#17692)) - fix: follow-up formatting in `print()` — flush block-level elements into separate sequences ([#17699](#17699)) - fix: preserve delegated event handlers as long as one or more root components are using them ([#17695](#17695)) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
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.
Follow-up to #17319.
The
Fragmentvisitor inprint()only flushed sequences onRegularElement, causing block-level elements (Component,SvelteHead,SvelteBoundary, etc.) to be lumped into the same sequence as adjacent nodes. This broke tools that programmatically manipulate the AST (e.g. sveltejs/cli#915).The fix flushes before and after all block-level element types, ensuring they get their own sequence and proper line separation.
Before
After