Simon Green
Simon Green
Probably too late to be helpful, but maybe useful for the next person who comes across this ... I too started reading through this app and found that it bears...
Just hit this problem with the emulator. Using [p-queue](https://www.npmjs.com/package/p-queue) to limit it to 2 concurrent uploads seems to always work, anything more and some never complete but also never fail,...
Dude, this repo is a demo app for developers, it isn't "Stripe Account Support". Even if it was, you don't provide any real detail that would be needed to enable...
Yes, any update to the store, even another property on an object, can end up triggering a prop change in a component when its values haven't really changed. IMO it's...
In case anyone needs a temporary fix: https://svelte-5-preview.vercel.app/#H4sIAAAAAAAAE41SQYrcMBD8Sq9YGBsG-25sQ0iekJziHLx2e9BGloTUnkwQ-nuQ5MizkyXsSVJTXVXqascWLtCy5rtjclyRNeyT1uzM6LcOD3tFQcjOzKrNTKHS2slwTf0gB-KrVobAwS_DaXwRCB4Wo1Y4pb7akjJ4uoN-VqtWEiXtuKrOlSr1nN4QTwZHwi84bxpNZq_qOVWqVxvwcqBJSUsQ9aDLfgoH11Fs2MAyCovgywObKKB7q1GUiW_Z5ERcSSB1uQgsSnChPFCUqDY9j4TFDboeDpGnWxVv4Mso5B-49q4Pcf1L1dbH6GX7shEpCUo2k-DTz84lo77_Gs-2ToD-PWhS9P23eN5BB-mek6koHv23R2ax2Lk0ueIeWXqoe3Zmq5r5wnFmDZkN_TlvVSb56G7hLa6AwF02jfK5gZCeElgJdSmS9sNoXPL-Pzf7-hxeXu29j1075_awISm-4EwbvIa7QdqMTEZDjHu-fIFkEZ66LoJz9AOFJ3T5c5TWhTLZX24_yHf-8sP_AR9atIi7AwAA
Svelte 5 has the same behavior in runes mode - i.e. the prop updates. So if that is an intended change it should be noted as breaking https://github.com/sveltejs/svelte/issues/11400 But for...
Yes, I found it from my first attempt upgrading some apps to 5. It isn't super-difficult to handle the change of behavior within the components but there is a real...
> It seems like a situation that would crucially rely on this effect should also have some kind of lifecycle or reactive check to work properly in most cases anyway....
The specific component applied some CSS animations in a sequence when it saw a boolean toggle change (when it hadn't actually changed, but something else in the same store managing...
No, it's passing a property value from the store when some other update is made - the deduper was to prevent the update triggering a prop change where there wasn't...