In class syntax, you cannot create non-reactive variables. about svelte HOT 3 CLOSED

You're running into an edge case here with the rerender heuristic. Svelte batches identifiers (foo) and member expressions (foo.bar) into one render effect to save memory and for better performance. The thought process is that identifiers cannot have side effects, and getters should never have.
In your case, everything's in one render effect, but it will only update if you actually modify a reactive variable. The last non-state is never updated because Svelte can detect that it's a non-reactive variable (because it's in scope and can be statically analyzed).
Closing as this heuristic was chosen deliberately.

from svelte.

@dummdidumm

I have understood your message through the translation.

In that case, how can we create non-reactive variables using class syntax? (It seems like you mentioned it's not possible...)
With functional syntax, non-reactive variables can be created and simply returned.

Am I correct in understanding that there is a difference in declaring non-reactive syntax between functional and class syntax, and that I should use functional syntax when necessary? (In other words, there are limitations with class syntax.)

from svelte.

The variable is not reactive in the sense that it will never trigger an update somewhere else. But if that variable happens to be read together with other variables that are in a reactive context and therefore rerun, then the current value will be used.

from svelte.