Guillaume Marcoux

Interesting! Thanks for the heads up :) And while I thought about running it twice indeed, I was thinking about the fact that it would essentially build twice for no...

Interesting, but if I read the specs correctly with the quote you added (I also added it just below), I think doing `value + step` would still be valid with...

Oh, I completely agree that it should work like the native spinner! Although I added in my latest edit that it is also broswer (well, *user-agent*...) dependant, so unless you...

With the removal of the `config.locale` option, I believe it would be possible to implement this validation based on Chrome's behavior : On changing value manually (**not** with the buttons),...

The issue is still there : > "*Note: When the data entered by the user doesn't adhere to the stepping configuration, the user agent may round to the nearest valid...

How convenient to find this issue now, I should've made one myself :)  Vite uses Rollup internally, so the problem happens with Vite too. I have a feeling it...

Well, if you are using Typescript, you may realize that using @bato3's technique or mine's above to import components with minimized build prevents you from using the types of these...

My best bet would be to trigger a timeout when the `active` prop changes that [dispatch](https://svelte.dev/tutorial/component-events) the introstart / introend / outrostart / outroend event based on the duration of...

I tried Live Share and this issue is one of the first thing we realized was happening - the undo stack is shared. I personally find value in having my...

@daytonellwanger I've read the conversations over in that other issue and indeed liked the idea of having a local and global undo stack that could be assigned to different keybinds....