Comments (4)
Just chipping in... I agree it seems to be a regression.
It seems to be related to the same prop being assigned the same value from two different components.
Here is a smaller example with runes.
And here is the same example without runes.
Both are failing in Svelte 5.
When you click the button, myProp
is updated but the component is never re-rendered.
Putting the last example into Svelte 4 works fine.
from svelte.
I believe the minimum reproduction is this. It seems that a derived value getting read, then another dependency triggering a rerun which results in the same value, and then a render effect reading the derived falsely makes that render effect believe nothing has changed. The other reproductions use props in a way that trigger the hardest variant of the internal props
function, which uses derived in a certain way.
from svelte.
Here is a smaller example with runes.
using bind:myProp={myProp}
fixes the issue
from svelte.
using
bind:myProp={myProp}
fixes the issue
Yeah. But this is a workaround.
from svelte.
Related Issues (20)
- Svelte 5: Event target is not retargeted after shadow dom
- Svelte 5: `nit` Duplicated text in documentation
- Linter error `no-unused-vars` if property is `$bindable` and never read HOT 2
- Svelte 5: state_referenced_locally warning on exported states
- Svelte 5: Again some events are ignored under these certain circumstances.
- Svelte 5 reactive map updates values given in constructor only after other data is updated
- `$state` looses reactivity with destructuring HOT 3
- Svelte5: default snippet inside component and overwriting on consuming HOT 6
- Reused element binding (`bind:this`) updates to `null` long after destruction HOT 3
- `" "` (space) in text nodes replaced with `""` (null string) in each blocks ([email protected]+) HOT 13
- $state rune in a .svelte.js/ts file not mutable from outside HOT 3
- Svelte 5 @next.148 broke Layercake HOT 3
- {#key} not working as parent of {#if} block HOT 2
- Svelte 5: effect_update_depth_exceeded with a simple code HOT 9
- Svelte 5 cannot delete items from initialized reactive `new Set([...])`
- Svelte 5: Nested form control bindings causes runtime error HOT 10
- Svelte 5: is there a way to type `{...props}`? HOT 2
- A simple component without script tag generates broken code when compiled HOT 4
- Reactive Set .size not updated after .delete() HOT 1
- Svelte 5: Transition doesn't worked in nested if statements HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from svelte.