feat: Add sql.js
fallback for sqlite
in wasm
#614
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 PR adds support for another
SQLite
driversql.js
is a browser orientated driver which compilesSQLite
towasm
.Enabling the possibility to run cds with
@cap-js/sqlite
in more environments.For example
better-sqlite3
cannot be loaded into the defaultnpm
promoted online environmentrunkit
:https://runkit.com/bobdenos/cds-test
There are some limitations with
sql.js
when comparing tobetter-sqlite3
. Which is mostly that it uses more memory and is around 50% slower for running the@cap-js/sqlite
tests. Wherebetter-sqlite3
takes~10
seconds to run all tests. It takessql.js
~14
seconds, but all current tests are green. Which should be good enough for experimentation scenarios.