New WASM build #233
Merged
New WASM build #233
Conversation
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
simolus3
force-pushed
the
new-web-build
branch
from
73f313c to
9e29345
Compare
simolus3
force-pushed
the
new-web-build
branch
from
cca5b5e to
e675606
Compare
stevensJourney
approved these changes
Feb 12, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
This sets up a new way to build the WebAssembly modules with SQLite and the PowerSync core extension. It clones the upstream
sqlite3.dartrepository at a given tag and applies a patch to the build scripts to include the extension. The resulting WebAssembly files are also published with the workers when we tag a powersync release.The
setup_web.dartscript will use releases from this repository (and expect wasm files there) starting with the next minor version, 1.12.0. This gives us the opportunity to prepare a patch release to test the publishing workflow.Additionally, I've set up a small npm package that allows us to publish the compiled WebAssembly modules to npm. This allows us to use npm-aware CDNs to deliver the WebAssembly assets (useful for e.g. FlutterFlow users that can't include
.wasmassets in test mode).