chore(playground): refresh vendored WASM bundle with SQLR-6 engine#165
Merged
Conversation
Rebuild sdk/wasm (wasm-pack --target web --release) against the engine at 79eff1d so the /playground exposes aggregates / GROUP BY / DISTINCT / HAVING over JOIN results. Only the .wasm binary changes — the JS glue and type definitions are byte-identical (no API surface change). Verified by loading the vendored pkg directly and running joined GROUP BY / DISTINCT / HAVING queries (correct results incl. outer-join NULL handling). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
joaoh82
added a commit
that referenced
this pull request
Jun 11, 2026
…WASM (#170) Post-release chores for v0.14.0, mirroring #163/#165: - install snippets (README, docs/ask.md, docs/embedding.md) 0.13 -> 0.14 - site displayed version (web/src/lib/site.ts) 0.14.0 - vendored playground bundle rebuilt from the v0.14.0 engine, picking up SQLR-2 / SQLR-14 / SQLR-15 scope validation (JS bindings unchanged — no API delta, binary only) Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The
/playgroundWASM bundle is a pinned, vendored copy ofsdk/wasm/pkg/— it doesn't pick up engine changes until rebuilt and re-committed. This refreshes it againstmainat 79eff1d (#164), so the playground exposes the new SQL surface: aggregates /GROUP BY/DISTINCT/HAVINGover JOIN results, including qualifiedGROUP BY t.colkeys.Built with the documented flow (
examples/wasm-playground/README.md):cd sdk/wasm wasm-pack build --target web --release --out-dir pkg cp pkg/{sqlrite_wasm.js,sqlrite_wasm_bg.wasm,sqlrite_wasm.d.ts,sqlrite_wasm_bg.wasm.d.ts} ../../web/public/playground/pkg/Only
sqlrite_wasm_bg.wasmchanges — the JS glue and.d.tsfiles are byte-identical (the WASM API surface didn't change, only engine internals).Test plan
.wasmbytes through the same init path the browser uses) and ran joinedGROUP BY/DISTINCT/HAVINGqueries — correct results, includingCOUNT(col)skipping outer-join NULL padding.--target nodejsbuild of the SDK.npm run buildinweb/passes;/playgroundpage builds.🤖 Generated with Claude Code