svelte

Commit Graph

Author	SHA1	Message	Date
ComputerGuy	1e55c1f11e	DRY	2 days ago
ComputerGuy	54368558c0	fix?	2 days ago
ComputerGuy	1c00d7dd84	lint	2 days ago
ComputerGuy	02194d68f4	evaluate keys, remove closure for `ClassDeclaration`	2 days ago
ComputerGuy	4f757ef271	Merge branch 'main' into gh-17012	2 days ago
github-actions[bot]	da00abe116	Version Packages (#17037 ) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>	3 days ago
Rich Harris	b5e23a6d13	chore: tweak memoizer logic (#17042 )	3 days ago
Rich Harris	fc181cf611	chore: move `$effect` visitors (#17041 )	3 days ago
Rich Harris	9096680c2e	chore: use ESTree namespace imports (#17040 )	3 days ago
Rich Harris	b01647455c	chore: create_expression_metadata -> ExpressionMetadata (#17039 ) * chore: create_expression_metadata -> ExpressionMetadata * err whatever	3 days ago
Paolo Ricciuti	8368a4beb9	fix: better error message for global variable assignments (#17036 )	3 days ago
github-actions[bot]	e33f774877	Version Packages (#17035 ) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>	3 days ago
Rich Harris	657ec89caa	fix: ignore fork `discard()` after `commit()` (#17034 ) * fix: ignore fork `discard()` after `commit()` * fix message	3 days ago
github-actions[bot]	875a04170e	Version Packages (#17029 ) * Version Packages * minor not patch * Apply suggestions from code review --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Rich Harris <rich.harris@vercel.com>	3 days ago
Rich Harris	d8137b78a5	fix: less confusing names for inspect errors (#17026 ) * fix: less confusing names for inspect errors * fix * Update packages/svelte/src/internal/client/dev/inspect.js * fix	3 days ago
Simon H	b7f39b464a	fix: always allow `setContext` before first await in component (#17031 ) The previous check was flawed because EFFECT_RAN would be set by the time it is checked, since a promise in a parent component will cause a delay of the inner component being instantiated. Instead we have a new field on the component context checking if the component was already popped (if se we are indeed too late). Don't love it to have a field just for this but I don't see another way to reliably check it. Fixes #16629	3 days ago
Rich Harris	4eb432e941	chore: remove event hoisting (#17030 ) * chore: get rid of hoisted event handlers * remove unused stuff * simplify * wow we can delete so much more code. this makes me so happy * even more!	4 days ago
ComputerGuy	307e42fe9b	Merge branch 'main' into gh-17012	4 days ago
Rich Harris	c08ecba1b7	feat: forking (#17004 ) * chore: run boundary async effects in the context of the current batch * WIP * reinstate kludge * fix test * WIP * WIP * WIP * remove kludge * restore batch_values after commit * make private * tidy up * fix tests * update test * reset #dirty_effects and #maybe_dirty_effects * add test * WIP * add test, fix block resolution * bring async-effect-after-await test from defer-effects-in-pending-boundary branch * avoid reawakening committed batches * changeset * cheat * better API * regenerate * slightly better approach * lint * revert this whatever it is * add test * Update feature description for fork API * error if missing experimental flag * rename inspect effects to eager effects, run them in prod * regenerate * Apply suggestions from code review Co-authored-by: Simon H <5968653+dummdidumm@users.noreply.github.com> * tidy up * add some minimal prose. probably don't need to go super deep here as it's not really meant for non-framework authors * bit more detail * add a fork_timing error, regenerate * unused * add note * add fork_discarded error * require users to discard forks * add docs * regenerate * tweak docs * fix leak * fix * preload on focusin as well * missed a spot * reduce nesting --------- Co-authored-by: Simon H <5968653+dummdidumm@users.noreply.github.com>	4 days ago
Rich Harris	7434f21ed4	chore: configurable sandbox output (#17028 )	4 days ago
github-actions[bot]	4a214f786f	Version Packages (#17019 ) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>	4 days ago
Rich Harris	f45d9cfe2d	fix: better optimization of await expressions (#17025 )	4 days ago
Rich Harris	2e1dd489f6	fix: coordinate mount of snippets with await expressions (#17021 ) * fix: coordinate mount of snippets with await expressions * try this * deduplicate --------- Co-authored-by: Simon H <5968653+dummdidumm@users.noreply.github.com>	4 days ago
ComputerGuy	5565d06bc1	fix	5 days ago
ComputerGuy	17308a5a4c	lint	5 days ago
ComputerGuy	7948cb928f	generate types	5 days ago
ComputerGuy	ded9f05901	fix one test	5 days ago
ComputerGuy	10e90c7e5a	fix?	5 days ago
ComputerGuy	f568190ac7	Merge branch 'gh-17012' of https://github.com/sveltejs/svelte into gh-17012	5 days ago
ComputerGuy	043fe1e3f9	deconflict number keys	5 days ago
ComputerGuy	07040d1005	Merge branch 'main' into gh-17012	5 days ago
ComputerGuy	686238bee8	tweak	5 days ago
ComputerGuy	2ed0f2f797	more	5 days ago
ComputerGuy	5f93015f74	fix	5 days ago
ComputerGuy	2edb05172a	init	5 days ago
Rich Harris	523c85bd3d	merge	5 days ago
Rich Harris	4e847cfd14	merge main	5 days ago
Rich Harris	0b477871e8	fix: coordinate mount of snippets with await expressions	5 days ago
Simon H	bd697c12c6	fix: flush pending changes after rendering `failed` snippet (#16995 ) fixes #16730	5 days ago
Simon H	cd3a11edff	fix: take into account static blocks when determining transition locality (#17018 ) The "is this a transparent effect we can ignore" logic for determining whether or not to play a local transition didn't account for pruned block effects. This fix marks the child branch as transparent if the block effect was, and during traversal then checks if the branch is the child of a block - if not that means it's the child of a pruned block effect. fixes #16826	5 days ago
github-actions[bot]	86aedaecf9	Version Packages (#17009 ) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>	5 days ago
Simon H	16117d9b69	perf: skip repeatedly traversing the same derived (#17016 ) * perf: skip repeatedly traversing the same derived We introduce a new flag which marks a derived during the mark_reaction phase and lift it during the execution phase. * fix This introduces a new flag which marks a derived as visited during the mark_reaction phase and lifts it during the dirty-check/execution phase (both are necessary because not all deriveds are necessarily executed, but they're always checked). We could've used a Set on mark_reactions which would've been simpler to reason about, alas it was performing consistenly worse on the kairo_mux_unowned / kairo_mux_owned benchmarks (it kinda makes sense generally, creating and filling a set is more expensive than juggling flags). Closes #16658, which showcases are particularly gnarly signal graph where many deriveds point to the same deriveds, where we would be traversing the same reactions over and over if we didn't do this. I also added a similar measure (this time a set/map is unavoidable/makes more sense) for mark_effects, hopefully this helps for #16990	5 days ago
dependabot[bot]	a28904c87a	chore(deps): bump vite from 5.4.20 to 7.1.11 (#17006 ) Bumps [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) from 5.4.20 to 7.1.11. - [Release notes](https://github.com/vitejs/vite/releases) - [Changelog](https://github.com/vitejs/vite/blob/main/packages/vite/CHANGELOG.md) - [Commits](https://github.com/vitejs/vite/commits/v7.1.11/packages/vite) --- updated-dependencies: - dependency-name: vite dependency-version: 7.1.11 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>	6 days ago
Rich Harris	851da4b629	chore: exclude vite optimized deps from stack traces (#17008 )	6 days ago
github-actions[bot]	3009a0208f	Version Packages (#16992 ) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>	6 days ago
Rich Harris	7e40186a5f	fix: run batch until complete (#16971 ) at present we only call batch.increment() when something async happens if we're not inside a pending boundary, but that's incorrect — it means that a batch is committed before everything resolves. When work inside a pending boundary does resolve, the batch becomes a zombie. At the same time, we don't handle effects inside pending boundaries correctly. They should be deferred until the boundary (and all its parents) are ready. This PR attempts to fix that — during traversal, when we exit a pending boundary, any effects that were collected get deferred until the next flush. We also distinguish between batch.#pending (any ongoing async work) and batch.#blocking_pending (any async work that should prevent effects outside pending boundaries from being flushed).	6 days ago
Rich Harris	4b32d6d8b3	fix: make `$inspect` logs come from the callsite (#17001 ) * fix: make `$inspect` logs come from the callsite * default to showing stack trace * reuse id * DRY out, improve server-side inspect * update docs * ugh * fix the dang tests * ugh windows is there no punch bowl you won't poop in? * argh * how about this * alright finally	6 days ago
dependabot[bot]	5bb28c4567	chore(deps-dev): bump vite from 7.1.5 to 7.1.11 (#16989 ) Bumps [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) from 7.1.5 to 7.1.11. - [Release notes](https://github.com/vitejs/vite/releases) - [Changelog](https://github.com/vitejs/vite/blob/main/packages/vite/CHANGELOG.md) - [Commits](https://github.com/vitejs/vite/commits/v7.1.11/packages/vite) --- updated-dependencies: - dependency-name: vite dependency-version: 7.1.11 dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>	7 days ago
Simon H	a57868ebce	fix: don't preserve reactivity context across function boundaries (#17002 ) Fixes #16809 We gotta take into account function boundaries when determining whether or not we're inside a derived (or const).	7 days ago
David	f549478dd0	fix: guard contents updated before the guard itself (#16930 ) Fixes #16850, fixes #16775, fixes #16795, fixes #16982 #16631 introduced a bug that results in the effects within guards being evaluated before the guards themselves. This fix makes sure to iterate the block effects in the correct order (top down) --------- Co-authored-by: Simon H <5968653+dummdidumm@users.noreply.github.com> Co-authored-by: Simon Holthausen <simon.holthausen@vercel.com>	1 week ago

1 2 3 4 5 ...

10696 Commits (1e55c1f11e18c2f28607c8a11eb2efa8f876dd9a) All Branches Search

10696 Commits (1e55c1f11e18c2f28607c8a11eb2efa8f876dd9a)

All Branches