[fix]destroy empty component

[magentaqin]

destroy empty component and fix fragment property value consistency as discussed in #7488

Before submitting the PR, please make sure you do the following

• It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
• Prefix your PR title with [feat], [fix], [chore], or [docs].
• This message body should clearly illustrate what problems it solves.
• Ideally, include a test that fails without this PR but passes with it.

Tests

• Run the tests with npm test and lint the project with npm run lint

[baseballyama]

Could you please add test?

[magentaqin]

Could you please add test?

OK. I will add test later.

[magentaqin]

@baseballyama Already pushed. Have a look at it. 🤝

[baseballyama]

Sorry for the comments many times but I think we need to update the test!

[magentaqin]

Sorry for the comments many times but I think we need to update the test!

😁 Indeed no bother at all, as concise code and better solution is what we both pursue. Thanks for your effort on careful reviewing. Already pushed. Have a look.

[magentaqin]

@baseballyama Is this PR ready to merge?

[baseballyama]

Yeah, it looks good to me but we need a review by at least one maintainer.

[magentaqin]

Hi, @tanhauhau, could you please have a look at this PR ? I've noticed that you have committed " add typescript def for transitions (#5625)" to this file runtime/internal/transitions.ts, and this PR is related to transition_out function.

[magentaqin]

Hi, @dummdidumm , could you please have a look at this PR? It's a little bugfix and has been opened for 2 months.