feat: package sqlite kv-store backend for stricter browser envs#23089
Merged
mverzilli merged 5 commits intoMay 13, 2026
Conversation
… builds Adds a package-internal subpath import (#msgpackr) with a 'browser' condition pointing at msgpackr/index-no-eval. Node consumers continue to get the regular runtime-codegen build. Browser bundlers automatically pick the CSP-safe variant via the standard browser condition. Also updates vitest.config.ts to explicitly include msgpackr/index-no-eval in optimizeDeps to avoid Vite discovery warnings during browser tests. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Upstream ordered-binary performs dynamic code generation at module-init to set up an unrolled string reader. That trips MV3 CSP and there's no CSP-safe shipped build. We only consume three symbols (toBufferKey, fromBufferKey, MAXIMUM_KEY) and none touch the dynamically-generated readString path, so vendor a minimal CSP-safe implementation under #ordered-binary's browser condition. Node consumers still get upstream. A parity test on a representative key set guards against divergence on future bumps. Also adds Buffer.compare as a static method to the browser Buffer stub so the parity test can byte-compare outputs in browser (Chromium) mode. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Thunkar
approved these changes
May 8, 2026
…/wallet-sdk-browser-entry-point
Collaborator
Flakey Tests🤖 says: This CI run detected 1 tests that failed, but were tolerated due to a .test_patterns.yml entry. |
AztecBot
pushed a commit
that referenced
this pull request
May 13, 2026
While the current sqlite backend for kv-store works fine in vanilla browser environments, browser policies can be stricter for extensions. For example, Chromium's MV3 doesn't accept extensions using `eval` or freely instantiating `Function`'s. This PR deals with said issues so that eventual wallet implementers don't have to. --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Collaborator
|
✅ Successfully backported to backport-to-v4-next-staging #23236. |
AztecBot
added a commit
that referenced
this pull request
May 14, 2026
BEGIN_COMMIT_OVERRIDE feat: package sqlite kv-store backend for stricter browser envs (#23089) fix(pxe): sync target contract before cross-contract utility call (#23225) fix(ci): swap slack_notify args in CLI acceptance test (#23241) feat: optimize get next app tag as sender (#23239) fix(noir): noirfmt nested_utility_contract main.nr (#23246) chore(aztec-nr): mark emit_event_in_public as #[inline_never] to shrink public dispatch (#23161) END_COMMIT_OVERRIDE
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.
While the current sqlite backend for kv-store works fine in vanilla browser environments, browser policies can be stricter for extensions. For example, Chromium's MV3 doesn't accept extensions using
evalor freely instantiatingFunction's. This PR deals with said issues so that eventual wallet implementers don't have to.