Sometimes it crashes (same condition is true and false at the same time)

[simonferndriger]

Here is an example: search.active is both true and false at the same time. It gets usually triggered by a keyboard event, but that might be just random.

[simonferndriger]

I can now stedily reproduce it (in my semi-complex app), and the only thing I see in the console are some unrelated warnings.

[simonferndriger]

Ah, I could solve it by listening in the body just for @keyup instead of @keyup.window. Even though I used $event.stopPropagation() it was received 12 times in a very short amount of time, I guess this was just too much stress for AlpineJS

[ekwoka]

Hard to say exactly without a recreation, but it could just be related to how the scheduler tries to batch work and prevent circular effects. That they get scheduled and run in a manner that could allow a value to change in between.