Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork4.6k
Comparing changes
Open a pull request
base repository:sveltejs/svelte
Uh oh!
There was an error while loading.Please reload this page.
base:fcfbc9c
head repository:sveltejs/svelte
Uh oh!
There was an error while loading.Please reload this page.
compare:27c90df
- 16commits
- 65files changed
- 9contributors
Commits on Jul 17, 2025
fix: robustify reset calls in error boundaries (#16171)
Fixes#16134* Add a warning when the misuse of `reset` in an `error:boundary` causes an error to be thrown when flushing the boundary content* Prevent uncaught errors to make test fails when they are expected and are fired during template effects flush* reset should just be a noop after the first call* correctly handle errors inside boundary during reset* handle errors in the correct boundary---------Co-authored-by: Rich Harris <rich.harris@vercel.com>
docs: remove mention of deprecated way to enhance typings (#16416)
Since#9070 it's prefered to use the "enhance svelte elements" way of doing things. That's so long ago that we can now remove the other option from the docs, and eventually remove the backwards compatibility that still allows the old way of doing things.
chore: cleanup obselete stuff (#16412)
* Update vitest.config.js* Update vitest.config.js* cleanup* woops* Update eslint.config.js---------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: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Commits on Jul 18, 2025
chore: Switch
payload.out
to an array (#16428)* chore: Switch `payload.out` to an array* Apply suggestions from code review* changeset
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Commits on Jul 19, 2025
fix: don't reexecute derived with no dependencies on teardown (#16438)
The prior logic was wrong because it reexecuted when something was clean, but we want to when it's not. The remaining fix was to also check the reactions: If an effect is destroyed and it was the last reaction of a derived then the derived is set to `MAYBE_DIRTY`. We therefore also need to check if the derived still has anyone listening to it, and only then reexecute it.Fixes#16363
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:git diff fcfbc9c...27c90df
Uh oh!
There was an error while loading.Please reload this page.