Skip to content

fix: follow-up formatting in print() for block-level elements#17699

Merged
Rich-Harris merged 1 commit intomainfrom
feat/print
Feb 13, 2026
Merged

fix: follow-up formatting in print() for block-level elements#17699
Rich-Harris merged 1 commit intomainfrom
feat/print

Conversation

@jycouet
Copy link
Contributor

@jycouet jycouet commented Feb 13, 2026

Follow-up to #17319.

The Fragment visitor in print() only flushed sequences on RegularElement, 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

<svelte:head><title>Page Title</title></svelte:head><div>no space</div>
<Component /><Component />
<Component><span>child</span></Component><div>after component</div>
<svelte:boundary><div>boundary content</div></svelte:boundary><div>after boundary</div>
<!--comment--><div>after comment</div>
<div>before comment</div>
<!--comment-->

{#each items as item}
	<div>{item}</div>
{/each}<div>after each</div>

{@render children()}<div>after render</div>
<div>before render</div>
{@render children()}

After

<svelte:head><title>Page Title</title></svelte:head>
<div>no space</div>
<Component />
<Component />
<Component><span>child</span></Component>
<div>after component</div>
<svelte:boundary><div>boundary content</div></svelte:boundary>
<div>after boundary</div>
<!--comment-->
<div>after comment</div>
<div>before comment</div>
<!--comment-->

{#each items as item}
	<div>{item}</div>
{/each}

<div>after each</div>
{@render children()}
<div>after render</div>
<div>before render</div>
{@render children()}

@changeset-bot
Copy link

changeset-bot bot commented Feb 13, 2026

🦋 Changeset detected

Latest commit: ef6d721

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
svelte Patch

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

@jycouet jycouet deployed to Publish pkg.pr.new (maintainers) February 13, 2026 15:43 — with GitHub Actions Active
@svelte-docs-bot
Copy link

@github-actions
Copy link
Contributor

Playground

pnpm add https://pkg.pr.new/svelte@17699

Copy link
Member

@Rich-Harris Rich-Harris left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

niiiice

@Rich-Harris Rich-Harris merged commit 86d5522 into main Feb 13, 2026
21 checks passed
@Rich-Harris Rich-Harris deleted the feat/print branch February 13, 2026 17:03
@github-actions github-actions bot mentioned this pull request Feb 13, 2026
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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants