Repository navigation
feat: BrowserDb query cursor and v3 core (v3) - #4
Merged
Merged
Conversation
Builds against the unreleased v3 core by git revision (switches to =3.0.0 at the release), which adds BrowserDb.query() returning a BrowserCursor (vars, nextBatch with JSON rows, close) (project-minigraf/minigraf#462). The README documents the cursor and why the file-backed parts of project-minigraf/minigraf#465 (read_only and the other file options) and #467 (LogWriter, not built on wasm32) do not apply in the browser. It also fixes the quick start, which used MiniGrafDb.inMemory() and a synchronous execute(); the package exports BrowserDb, whose execute() is async. CI runs on PRs to v3, and on this branch the WASI binary is built from core's v3 branch. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015GgLEs8YozJjYhwPEYgTUn
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.
The browser part of project-minigraf/minigraf#462, #465 and #467, following minigraf's
docs/superpowers/specs/2026-10-07-binding-etl-surface-design.md(minigraf PR #468).What's new
minigrafis a git dependency on the corev3commit from PR #468. That commit addsBrowserDb.query(datalog)→BrowserCursor(vars(),nextBatch(n)with JSON rows orundefined,close(); non-queries throw API-012). This repo re-exports core, sowasm-pack buildpicks it up. Checked in the generatedminigraf_wasm.d.ts.read_onlyand the other file-backed options (#465) andLogWriter(#467, not built for wasm32) don't apply to the IndexedDB-backedBrowserDb, and that the fact log is not exposed in the browser.MiniGrafDb.inMemory()with a synchronousexecute(). The package exportsBrowserDb(await BrowserDb.open(name)/openInMemory()), and itsexecute()is async.v3, and on this branch the WASI binary job builds from core'sv3. The WASI package ships the REPL binary, so nothing new is exposed there.Testing
wasm-pack build --target web --features browsersucceeds, and the.d.tshasBrowserCursor.wasm-bindgen-testbrowser tests in PR #468 (headless Firefox, 12 passed).🤖 Generated with Claude Code
https://claude.ai/code/session_015GgLEs8YozJjYhwPEYgTUn