UGA Finance and Real Estate.
No open PRs to review
No open issues to review
tailwind-merge as a dev tool, not a dependency
Profile
A SvelteKit adapter for Bun
The Svelte Language Server, and official extensions which use it
PostCSS plugin to inline at-import rules content
A utility-first CSS framework for rapid UI development.
Scroll probe for sveltejs/kit#11452: pushState + history.back() across kit 2.0.7 / 2.70.0 / 3.0.0-next.9
Minimal Svelte-only repro: component double-mounts under experimental.async (from sveltejs/kit#16166)
Incredibly fast JavaScript runtime, bundler, test runner, and package manager – all in one
shadcn/ui, but for Svelte. ✨
web development, streamlined
- fix: call `onerror` and provide a working `reset` when hydrating a failed boundary
One asymmetry I noticed while writing this but left alone. In `#handle_error` the failed snippet is rendered with `effect.b = this` and `BOUNDARY_EFFECT`, and errors thrown inside it are routed throu…
- A `<svelte:boundary>` hydrated in the failed state can never be reset
The docs already specify this behavior. From [the boundary docs](https://svelte.dev/docs/svelte/svelte-boundary): > If the boundary has an `onerror` handler, it will be called upon hydration with the…
- experimental.async: nested dynamic component mounts twice when swapped while a persistent ancestor renders the outgoing subtree's teleporte…
Narrowed this down, empirically and in the source. I added a `closest('.teleport-target')` check to the leaf's `onMount` (not in the repro repo). The two instances mount in different places, the firs…
- Provide hasContext function with createContext
Nice find, that's the focused issue I meant, so nothing new to open. Adding your use case there and linking this thread is the bump, that kind of evidence is what the team said they'd wait for. I'd h…
- feat: add `onchange` option to `$state`
The eager effect machinery from #17934 answers most of what this stalled on, sync dispatch inside `set()`, fork behaviour, the array double-fire, so I had a go at the one piece left, deep propagation…
- Async `$effect.root()`
An owner API would not be enough on its own. Context surviving an `await` is a compiler transform (`$.save()` around awaits in reactive positions), so in an uncompiled test body `$effect` still throw…