Releases: sveltejs/svelte
svelte@5.0.0-next.148
svelte@5.0.0-next.147
svelte@5.0.0-next.144
Patch Changes
-
fix: address derived memory leak on disconnection from reactive graph (#11819)
-
fix: set correct scope for
@const
tags within slots (#11798) -
fix: better support for onwheel events in chrome (#11808)
-
fix: coherent infinite loop guard (#11815)
-
fix: make prop fallback values deeply reactive if needed (#11804)
-
fix: robustify initial scroll value detection when scroll is smooth (#11802)
svelte@5.0.0-next.143
Patch Changes
- feat: provide
Component
type that represents the new shape of Svelte components (#11775)
svelte@5.0.0-next.142
Patch Changes
-
fix: allow runelike writable as prop (#11768)
-
fix: support
array.lastIndexOf
without second argument (#11766) -
fix: handle
this
parameter in TypeScript-annotated functions (#11795) -
fix: allow classes to be reassigned (#11794)
-
fix: capture the correct event names when spreading attributes (#11783)
-
fix: allow global next to
&
for nesting (#11784) -
fix: parse ongotpointercapture and onlostpointercapture events correctly (#11790)
-
fix: only inject push/pop in SSR components when necessary (#11771)
svelte@5.0.0-next.141
svelte@5.0.0-next.140
Patch Changes
- breaking: event handlers + bindings now yield effect updates (#11706)
svelte@5.0.0-next.139
Patch Changes
- fix: ensure we clear down each block opening anchors from document (#11740)
svelte@5.0.0-next.138
Patch Changes
-
fix: allow comments after last selector in css (#11723)
-
fix: don't add scoping modifier to nesting selectors (#11713)
-
chore: speedup hydration around input and select values (#11717)
-
fix: update value like attributes in a separate template_effect (#11720)
-
fix: improve handling of unowned derived signal (#11712)
svelte@5.0.0-next.137
Patch Changes
-
fix: migrate derivations without semicolons (#11704)
-
fix: check for invalid bindings on window and document (#11676)
-
fix: more efficient spread attributes in SSR output (#11660)
-
fix: inline pointer events now correctly work in Chrome (#11695)
-
fix: don't require warning codes to be separated by commas in non-runes mode (#11669)