Skip to content

fix: do not defer unmount; immediately unmount components #16624

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 5 commits into from
Aug 15, 2025

Conversation

harshmandan
Copy link
Contributor

@harshmandan harshmandan commented Aug 14, 2025

Description:

Do not defer unmounting of components. Unmount the components immediately. This changes fixes #16618 and brings back pre-async feature lifecycle order.

Tests and linting

  • Run the tests with pnpm test and lint the project with pnpm lint

Copy link

changeset-bot bot commented Aug 14, 2025

🦋 Changeset detected

Latest commit: 4f5ac21

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

Copy link
Contributor

Playground

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

@harshmandan harshmandan requested a review from jrmajor August 15, 2025 12:15
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.

thank you!

@Rich-Harris Rich-Harris merged commit 95e5175 into sveltejs:main Aug 15, 2025
12 checks passed
@github-actions github-actions bot mentioned this pull request Aug 15, 2025
@Rich-Harris
Copy link
Member

Actually I think we need to revert or revisit this.

This is my bad, I thought the PR was just reordering stuff within commit

@harshmandan
Copy link
Contributor Author

harshmandan commented Aug 16, 2025

Actually I think we need to revert or revisit this.

Saw the breaking example this morning. Already working on a fix.

Edit: Added a follow-up PR #16633

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.

Component lifecycle timing changed in 5.36 causing subscription overlap issues
4 participants