chore(sqlite3mc-wasm): bump SQLite3MultipleCiphers to 2.3.5 - #24293
Merged
Conversation
….53.2) Bumps the vendored sqlite3mc WASM build from 2.2.4 (SQLite 3.50.4) to 2.3.5 (SQLite 3.53.2). Upstream consolidated the bundler-friendly ES module into `sqlite3.mjs` (the old `sqlite3-bundler-friendly.mjs` is gone), so the wrapper entry, the locally-authored `.d.mts` companion, the vendor allowlist, and the vendor-script paths are updated to match. The new build feature-detects Node via `globalThis.process` instead of a bare `process` global, so the OPFS Web Worker bundles cleanly under vite-plugin-node-polyfills with no per-consumer worker config. It also brings three SQLite minor releases of fixes and query-planner improvements, plus the new opfs-wl (Web Locks) VFS. Validated: re-vendored via scripts/vendor.sh (zip SHA verified, SHA256SUMS regenerated), the wrapper and kv-store compile, and the full sqlite-opfs browser suite passes (112 tests, including the ChaCha20 encryption paths).
nchamo
approved these changes
Jun 25, 2026
Thunkar
added a commit
that referenced
this pull request
Jul 6, 2026
SQLite3MultipleCiphers 2.3.5 (#24293) stopped shipping the bundler-friendly build variant, so the package entry re-exports the plain sqlite3.mjs. That loader always resolves sqlite3.wasm through its Module['locateFile'] hook, which computes new URL(path, import.meta.url) with a dynamic path — invisible to bundlers. Bundled consumers (e.g. Vite apps using @aztec/kv-store/sqlite-opfs) request an unhashed sqlite3.wasm relative to the emitted chunk and 404 at runtime; dev servers are unaffected, so only production builds break. Wrap the init and inject emscriptenLocateFile (the vendored loader's supported escape hatch= resolving the wasm via a static `new URL('../vendor/jswasm/sqlite3.wasm', import.meta.url)` that bundlers detect, emit, and rewrite. Unbundled usage is unaffected: the static URL resolves to the real vendored path. Verified by building a Vite consumer against the patched dest/: the emitted worker chunk resolves the hashed wasm asset through the hook. 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
3 participants
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.
Bumps to the latest SQLite3mc release, which solves some module exporting issues
Closes F-744