fix: optimize the assign expression

[pgliang001]

Here, neither null or undefined again

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.
• If this PR changes code within packages/svelte/src, add a changeset (npx changeset).

Tests and linting

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

[pgliang001]

@Rich-Harris @Conduitry pls review the change

[paoloricciuti]

@Rich-Harris @Conduitry pls review the change

1. pls don't tag maintainers to review the code submitted 7 minutes ago, especially on a saturday
2. it would be useful to have more context around this change...what issue is fixing? What is str is null there?
3. please add a test case for this change

[Rich-Harris]

Thank you, the change is good since the str == null case has already been accounted for. But yeah, don't ever tag maintainers demanding that they review your code, especially if it's just been submitted. It's extremely rude.

[pgliang001]

Thank you, the change is good since the str == null case has already been accounted for. But yeah, don't ever tag maintainers demanding that they review your code, especially if it's just been submitted. It's extremely rude.

Oh sorry, my extremely mistake

[Ocean-OS]

Why not just text.nodeValue = str ?? '';?

[adiguba]

Why no even text.nodeValue = str ?

str is already non-null, and the type coercion will be done by the assignment...

[Ocean-OS]

Why no even text.nodeValue = str ?

str is already non-null, and the type coercion will be done by the assignment...

Oh wait, yeah! I didn't know it did that.