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>

…7002)Fixes#16809We gotta take into account function boundaries when determining whether or not we're inside a derived (or const).

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>

* 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

 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).

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>