feat: Initial fork and patching of sql.js #1
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
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.
This adds everything needed to maintain our fork of sql.js. This variant includes Powersync (made possible by the git patch files). To be used in the
@powersync/dev-adapterpackage introduced by powersync-ja/powersync-js#647.Why?
Considering that there are already production ready adapters for web, React Native (two in fact), and Node it might not be immediately clear why we need this. Those adapters are recommended for production. But this dev-adapter needs less setup, as it runs completely in JS. This simplifies the setup which is great for trying out PowerSync.
This also works with Expo Go because we don't need to do build config as it's already running in JS.