fix(web): emit sqlite3mc runtime assets unhashed so production builds… - #58
Merged
Merged
Conversation
… can load them
Since SQLite3MultipleCiphers 2.3.5 (aztec-packages#24293, in rc.2) the
sqlite3mc loader resolves sqlite3.wasm through Module['locateFile'] with a
dynamic path the bundler can't rewrite; production builds request unhashed
assets/sqlite3.wasm relative to the worker chunk and 404 ('unsupported
MIME type' follow-up). Dev is unaffected. Emit the wasm and the OPFS
async-proxy script under their original names at build time. Same fix as
aztec-kit's sqliteRuntimeAssetsPlugin.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
🚀 Web wallet deployed! Preview URL: https://demo-wallet-ooy8c0h42-thunkars-projects.vercel.app |
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.
… can load them
Since SQLite3MultipleCiphers 2.3.5 (aztec-packages#24293, in rc.2) the sqlite3mc loader resolves sqlite3.wasm through Module['locateFile'] with a dynamic path the bundler can't rewrite; production builds request unhashed assets/sqlite3.wasm relative to the worker chunk and 404 ('unsupported MIME type' follow-up). Dev is unaffected. Emit the wasm and the OPFS async-proxy script under their original names at build time. Same fix as aztec-kit's sqliteRuntimeAssetsPlugin.