History

Simon H 1ebed68322 fix: avoid traversing clean roots (#17928 ) Before #17805, all batches drew from the same `queued_root_effects` and did reset them to the empty array when starting a flush. After the refactoring roots are scheduled per batch. This introduces a possible race condition where the same root is scheduled multiple times. It was possible because of the rebase logic in `#commit` not clearing the array of roots, so if you somehow flush that same batch later, you will end up traversing a clean root. (it is possible a bug like this always existed with rebasing it was just impossible hard to trigger it before because everyone drew from the same root effects array) The fix is a bit more complicated than just checking if new roots where added, we gotta check if we actually created async work before traversing. Fixes #17918 --------- Co-authored-by: Rich Harris <rich.harris@vercel.com>		2 months ago
..
README.md	chore: setup changesets (#8668 )	3 years ago
config.json	chore: enter changeset prerelease mode	3 years ago
fix-select-stale-value.md	fix: keep select.__value current when effect is deferred (#17745 )	2 months ago
flat-lemons-joke.md	chore: add invariant utility (#17929 )	2 months ago
gold-times-see.md	fix: ensure deriveds values are correct across batches (#17917 )	2 months ago
purple-boats-hear.md	fix: handle async RHS in assignment_value_stale (#17925 )	2 months ago
stupid-chefs-rescue.md	fix: avoid traversing clean roots (#17928 )	2 months ago

README.md

Changesets

Hello and welcome! This folder has been automatically generated by @changesets/cli, a build tool that works with multi-package repos, or single-package repos to help you version and publish your code. You can find the full documentation for it in our repository

We have a quick list of common questions to get you started engaging with this project in our documentation