svelte

Commit Graph

Author	SHA1	Message	Date
Rich Harris	db41cc46cb	reset #dirty_effects and #maybe_dirty_effects	2 weeks ago
Rich Harris	fdc511416e	update test	2 weeks ago
Rich Harris	e31956de85	fix tests	2 weeks ago
Rich Harris	fc9699aa34	Merge branch 'main' into run-batch-until-complete	2 weeks ago
github-actions[bot]	7d9ea8ea99	Version Packages (#16984 ) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>	2 weeks ago
Rich Harris	b8627e511d	chore: centralise branch management (#16977 ) * WIP * WIP * WIP * WIP * WIP * fix hydration * simplify * all tests passing * key blocks * snippets * fix * tidy up * WIP await * tidy up * fix * neaten up * unused * tweak * elements * changeset * fix * preserve newer batches * add comment * add comment * no longer necessary apparently? * move legacy logic to key block	2 weeks ago
ComputerGuy	9a488d6b25	fix: place `let:` declarations before `{@const}` declarations (#16985 ) * fix: place `let:` declarations before `{@const}` declarations * lint * fix	2 weeks ago
Rich Harris	c8ef540985	fix: improve `each_key_without_as` error (#16983 )	2 weeks ago
github-actions[bot]	bd2d3db6d0	Version Packages (#16970 ) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>	2 weeks ago
Rich Harris	53f2693b3b	feat: `$state.eager(value)` (#16849 ) * WIP implement `$effect.pending(...)` * feat: `$state.eager(value)` (#16926) * runtime-first approach * revert these * type safety, lint * fix: better input cursor restoration for `bind:value` (#16925) If cursor was at end and new input is longer, move cursor to new end No test because not possible to reproduce using our test setup. Follow-up to #14649, helps with #16577 * Version Packages (#16920) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * docs: await no longer need pending (#16900) * docs: link to custom renderer issue in Svelte Native discussion (#16896) * fix code block (#16937) Updated code block syntax from Svelte to JavaScript for clarity. * fix: unset context on stale promises (#16935) * fix: unset context on stale promises When a stale promise is rejected in `async_derived`, and the promise eventually resolves, `d.resolve` will be noop and `d.promise.then(handler, ...)` will never run. That in turns means any restored context (via `(await save(..))()`) will never be unset. We have to handle this case and unset the context to prevent errors such as false-positive state mutation errors * fix: unset context on stale promises (slightly different approach) (#16936) * slightly different approach to #16935 * move unset_context call * get rid of logs --------- Co-authored-by: Rich Harris <rich.harris@vercel.com> * fix: svg `radialGradient` `fr` attribute missing in types (#16943) * fix(svg radialGradient): fr attribute missing in types * chore: add changeset * Version Packages (#16940) * Version Packages * Update packages/svelte/CHANGELOG.md --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Rich Harris <rich.harris@vercel.com> * chore: simplify `batch.apply()` (#16945) * chore: simplify `batch.apply()` * belt and braces * note to self * unused * fix: don't rerun async effects unnecessarily (#16944) Since #16866, when an async effect runs multiple times, we rebase older batches and rerun those effects. This can have unintended consequences: In a case where an async effect only depends on a single source, and that single source was updated in a later batch, we know that we don't need to / should not rerun the older batch. This PR makes it so: We collect all the sources of older batches that are not part of the current batch that just committed, and then only mark those async effects as dirty which depend on one of those other sources. Fixes the bug I noticed while working on #16935 * fix: ensure map iteration order is correct (#16947) quick follow-up to #16944 Resetting a map entry does not change its position in the map when iterating. We need to make sure that reset makes that batch jump "to the front" for the "reject all stale batches" logic below. Edge case for which I can't come up with a test case but it _is_ a possibility. * feat: add `createContext` utility for type-safe context (#16948) * feat: add `createContext` utility for type-safe context * regenerate * Version Packages (#16946) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * chore: Remove annoying sync-async warning (#16949) * fix * use `$state.eager(value)` instead of `$effect.pending(value)` --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Hyunbin Seo <47051820+hyunbinseo@users.noreply.github.com> Co-authored-by: Ben McCann <322311+benmccann@users.noreply.github.com> Co-authored-by: Rich Harris <rich.harris@vercel.com> Co-authored-by: Hannes Rüger <hannes@hannesrueger.de> Co-authored-by: Elliott Johnson <sejohnson@torchcloudconsulting.com> * decouple from boundaries * use queue_micro_task * add test * fix * changeset * revert * tidy up * update docs * Update packages/svelte/src/internal/client/reactivity/batch.js Co-authored-by: Simon H <5968653+dummdidumm@users.noreply.github.com> * minor tweak --------- Co-authored-by: Simon H <5968653+dummdidumm@users.noreply.github.com> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Hyunbin Seo <47051820+hyunbinseo@users.noreply.github.com> Co-authored-by: Ben McCann <322311+benmccann@users.noreply.github.com> Co-authored-by: Hannes Rüger <hannes@hannesrueger.de> Co-authored-by: Elliott Johnson <sejohnson@torchcloudconsulting.com>	2 weeks ago
Rich Harris	ee093e4c86	fix: preserve `<select>` state while focused (#16958 )	2 weeks ago
Rich Harris	9b5fb3f430	fix: error if `each` block has `key` but no `as` clause (#16966 )	2 weeks ago
Rich Harris	90e3148a56	tidy up	2 weeks ago
Rich Harris	46d61eeec6	make private	2 weeks ago
Rich Harris	09f4d75c2c	merge main	2 weeks ago
Rich Harris	7d977fad88	chore: run boundary async effects in the context of the current batch (#16968 )	2 weeks ago
github-actions[bot]	a54186242a	Version Packages (#16967 ) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>	2 weeks ago
Rich Harris	bba5314dab	restore batch_values after commit	2 weeks ago
Rich Harris	c054cd4f3f	remove kludge	2 weeks ago
Rich Harris	d8df737f56	WIP	2 weeks ago
Rich Harris	739f5fc1c6	WIP	2 weeks ago
Rich Harris	18ecf01382	WIP	2 weeks ago
Rich Harris	ae0038c953	fix test	2 weeks ago
Rich Harris	1e2958e5ac	reinstate kludge	2 weeks ago
Rich Harris	c3db9ac137	WIP	2 weeks ago
Rich Harris	7c1408d6df	chore: run boundary async effects in the context of the current batch	2 weeks ago
Paolo Ricciuti	8691391c08	fix: add hydration markers in `pending` branch of SSR boundary (#16965 )	2 weeks ago
github-actions[bot]	94fc836e3a	Version Packages (#16950 ) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>	3 weeks ago
Rich Harris	470d61221e	chore: tidy up (#16957 )	3 weeks ago
Rich Harris	d6d13ced08	docs: improve createContext documentation (#16952 ) * docs: improve createContext documentation * update context page * bump	3 weeks ago
Rich Harris	ec99d7bc4c	fix docs (#16953 )	3 weeks ago
Elliott Johnson	9cdd76e3a3	chore: Remove annoying sync-async warning (#16949 )	3 weeks ago
github-actions[bot]	005895d994	Version Packages (#16946 ) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>	3 weeks ago
Rich Harris	f3c55e8e6c	feat: add `createContext` utility for type-safe context (#16948 ) * feat: add `createContext` utility for type-safe context * regenerate	3 weeks ago
Simon H	99711d5822	fix: ensure map iteration order is correct (#16947 ) quick follow-up to #16944 Resetting a map entry does not change its position in the map when iterating. We need to make sure that reset makes that batch jump "to the front" for the "reject all stale batches" logic below. Edge case for which I can't come up with a test case but it _is_ a possibility.	3 weeks ago
Simon H	28765f846e	fix: don't rerun async effects unnecessarily (#16944 ) Since #16866, when an async effect runs multiple times, we rebase older batches and rerun those effects. This can have unintended consequences: In a case where an async effect only depends on a single source, and that single source was updated in a later batch, we know that we don't need to / should not rerun the older batch. This PR makes it so: We collect all the sources of older batches that are not part of the current batch that just committed, and then only mark those async effects as dirty which depend on one of those other sources. Fixes the bug I noticed while working on #16935	3 weeks ago
Rich Harris	d50701d277	unused	3 weeks ago
Rich Harris	a7c958a2a5	chore: simplify `batch.apply()` (#16945 ) * chore: simplify `batch.apply()` * belt and braces * note to self	3 weeks ago
github-actions[bot]	2a951391dc	Version Packages (#16940 ) * Version Packages * Update packages/svelte/CHANGELOG.md --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Rich Harris <rich.harris@vercel.com>	3 weeks ago
Hannes Rüger	e8330ee7bf	fix: svg `radialGradient` `fr` attribute missing in types (#16943 ) * fix(svg radialGradient): fr attribute missing in types * chore: add changeset	3 weeks ago
Simon H	23e2bb3b89	fix: unset context on stale promises (#16935 ) * fix: unset context on stale promises When a stale promise is rejected in `async_derived`, and the promise eventually resolves, `d.resolve` will be noop and `d.promise.then(handler, ...)` will never run. That in turns means any restored context (via `(await save(..))()`) will never be unset. We have to handle this case and unset the context to prevent errors such as false-positive state mutation errors * fix: unset context on stale promises (slightly different approach) (#16936) * slightly different approach to #16935 * move unset_context call * get rid of logs --------- Co-authored-by: Rich Harris <rich.harris@vercel.com>	3 weeks ago
Rich Harris	b05e12fd63	fix code block (#16937 ) Updated code block syntax from Svelte to JavaScript for clarity.	3 weeks ago
Ben McCann	ba782f9fde	docs: link to custom renderer issue in Svelte Native discussion (#16896 )	3 weeks ago
Hyunbin Seo	b91f9de129	docs: await no longer need pending (#16900 )	3 weeks ago
github-actions[bot]	420468a041	Version Packages (#16920 ) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>	3 weeks ago
Simon H	5d9b4c66ca	fix: better input cursor restoration for `bind:value` (#16925 ) If cursor was at end and new input is longer, move cursor to new end No test because not possible to reproduce using our test setup. Follow-up to #14649, helps with #16577	3 weeks ago
7nik	93012e1e6f	fix: track the user's getter of `bind:this` (#16916 )	3 weeks ago
Paolo Ricciuti	297afd0578	fix: generate correct code for `each` blocks with async body (#16923 ) * fix: generate correct code for `each` blocks with async body * fix: else branch of `each` block * chore: add expected html	3 weeks ago
Paolo Ricciuti	7f8e60fd8a	fix: generate correct SSR code for the case where `pending` is an attribute (#16919 ) Closes #16886	3 weeks ago
Simon H	9c350cfdab	chore: test for batches flush fix (#16915 ) Test for #16912 Also some explanation what the bug was: 1. async batch kicks off 2. outer async work succeeds, still something pending, so doesn't do anything for now 3. something unrelated writes to a signal (in the remote functions case it's the query writing to loading, raw etc), which creates a new batch 4. new batch executes. since there are multiple batches it takes the previous value which means if block is still alive. commits that, since no async work from the perspective of this branch 5. inner async work succeeds. now the batch has zero pending async work so it can flush. But the if block is no longer dirty since it was done by the other batch already -> never undos the other work #16912 fixes it by still traversing the tree which means the if block deletion is scheduled to commit later, which it then does	4 weeks ago

1 2 3 4 5 ...

10662 Commits (db41cc46cb85d24e1bc15da334f028314b059b5a) All Branches Search

10662 Commits (db41cc46cb85d24e1bc15da334f028314b059b5a)

All Branches