I know nothing about wasm so we need to find someone kind enough to validate this PR.
And would you mind adding a dedicated job, something like https://github.com/rusqlite/rusqlite/pull/1010/files#diff-7829468e86c1cc5d5133195b5cb48e1ff6c75e3e9203777f6b2e379d9e4882b3R86
in your PR
Thanks.

(a) https://github.com/Spxg/sqlite-wasm-rs/blob/master/sqlite-wasm-rs/sqlite-wasm/sqlite3.wasm
comes from
https://sqlite.org/2025/sqlite-wasm-3490000.zip
?
(b) You don't use https://github.com/sqlite/sqlite/blob/master/ext/wasm/api/sqlite3-wasm.c ?

I know nothing about wasm so we need to find someone kind enough to validate this PR. And would you mind adding a dedicated job, something like https://github.com/rusqlite/rusqlite/pull/1010/files#diff-7829468e86c1cc5d5133195b5cb48e1ff6c75e3e9203777f6b2e379d9e4882b3R86 in your PR Thanks.

Of course, I will add the tests runner to CI/CD later today, currently all the tests pass (except a couple that require std::fs)

(a) https://github.com/Spxg/sqlite-wasm-rs/blob/master/sqlite-wasm-rs/sqlite-wasm/sqlite3.wasm comes from https://sqlite.org/2025/sqlite-wasm-3490000.zip ? (b) You don't use https://github.com/sqlite/sqlite/blob/master/ext/wasm/api/sqlite3-wasm.c ?

(a) sqlite3.wasm is only used in wrapper feature, and the interface is exported through wasm-bindgen. The sqlite3.wasm in the project is not from the official product, see https://github.com/Spxg/sqlite-wasm-rs?tab=readme-ov-file#why-vendor-sqlite-wasm

(b) This file is used to compile sqlite3 into emscripten wasm, mainly for generating bindings in emscripten js. We don't need it, we have enabled -DSQLITE_OS_OTHER, and do not compile sqlite directly into .wasm, and we don't need emscripten js binding.

The tests have been added to the CI/CD (approval is required to verify whether they work). All tests have passed in local testing.
The rusqlite_test_helper library has been added to handle the differences between the wasm platform and the native platform.

Thanks for your time and explanations.

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 82.08%. Comparing base (44e0ef9) to head (8e53118).

@@            Coverage Diff             @@
##           master    #1643      +/-   ##
==========================================
- Coverage   86.90%   82.08%   -4.82%     
==========================================
  Files          58       58              
  Lines       10638     7398    -3240     
==========================================
- Hits         9245     6073    -3172     
+ Misses       1393     1325      -68     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Fixed CI for clippy and minimal versions. The reduced coverage is probably because I added two wasm-only tests and some comments.

By the way, why does the CI process require approval? It seems that it is not convenient to find problems and fix CI.

Fixed CI for clippy and minimal versions. The reduced coverage is probably because I added two wasm-only tests and some comments.

By the way, why does the CI process require approval? It seems that it is not convenient to find problems and fix CI.

Maybe because a patched / malicious build.rs, you can do anything !

Maybe because a patched / malicious build.rs, you can do anything !

Reasonable. I need to rerun CI now to verify whether everything passes. Can you approve it?

By the way, why does the CI process require approval? It seems that it is not convenient to find problems and fix CI.

You can enable Actions on your fork and get CI to run inside your account instead of from the PR.

By the way, why does the CI process require approval? It seems that it is not convenient to find problems and fix CI.

You can enable Actions on your fork and get CI to run inside your account instead of from the PR.

Thanks!

CI have passed: https://github.com/Spxg/rusqlite/actions/runs/13284078817/job/37088729090, cov failed because I didn’t have a token to upload. (thanks to @trevyn )

I'm ready for the review.

Because of breaking changes, sqlite-wasm-rs is updated to 0.3

1. Deleted wrapper feature
2. Use bundled feature to compile sqlite by default
3. Provided precompiled feature, see https://github.com/Spxg/sqlite-wasm-rs#why-provide-precompiled-library for details

we need to find someone kind enough to validate this PR.

Any suggestions?

we need to find someone kind enough to validate this PR.

Any suggestions?

Maybe @thomcc or @trevyn ?

This PR is exactly what I need for one of my projects, so I hope someone can validate it soon.

I can at least confirm @Spxg 's fork works without issue when used as a dependency in a project targeting wasm32-unknown-unknown. I only seem to be able to get it to work in-memory for wasm builds though, and am not sure how to get it to work with a persistent VFS.

and am not sure how to get it to work with a persistent VFS.

Currently, there is only one option for persistence: opfs-sahpool, which is ported from sqlite-wasm (https://sqlite.org/wasm/doc/trunk/persistence.md#vfs-opfs-sahpool) and needs to run on a dedicated worker. Other VFS are more difficult to implement, such as VFS based on IndexedDB, because they are asynchronous and require a lot of extra work: rhashimoto/wa-sqlite#154 (comment)

For more usages, see https://github.com/Spxg/sqlite-wasm-rs/blob/master/VFS.md#opfs-sahpool. This interface is now re-exported by rusqlite, and can be installed using rusqlite::ffi::install_opfs_sahpool.

am not sure how to get it to work with a persistent VFS.

If you are interested, here is an example I wrote for diesel, which can easily experience the difference between memory vfs and persistent vfs: https://github.com/diesel-rs/diesel/tree/master/examples/sqlite/wasm. (bundled feature is used by default, which requires the emscripten toolchain. If you don't have the emscripten toolchain, change feature to precompiled)

Precompiled products are not provided by default, you can specify the precompiled-wasm feature.
Using the bundled feature requires the emscripten toolchain.

See https://github.com/Spxg/sqlite-wasm-rs/?tab=readme-ov-file#why-provide-precompiled-library for details.

@Spxg Thanks for the information!

Maybe @thomcc or @trevyn ?

It seems like they all don't have time to review it, so I thought of some questions you might be concerned about, I hope this can answer your questions.

• Why rusqlite_test_helper macro provided?
  Because the test of wasm32-unknown-unknown uses #[wasm_bindgen_test] instead of #[test], cfg_attr must be used to distinguish the behavior of different platforms, rusqlite_test_helper is provided to complete this task simply and cleanly.


• Why precompiled-wasm feature is provided?
  Because most rust users may not have the emscripten toolchain, precompiled products are provided. Considering the downstream's security concerns, precompiled products are compiled and signed through github action (like https://github.com/Spxg/sqlite-wasm-rs/attestations/5145105), and bundled features are also provided. For details, see https://github.com/Spxg/sqlite-wasm-rs?tab=readme-ov-file#why-provide-precompiled-library. For this reason, users who use rusqlite must specify bundled or precompiled-wasm features.

• Why sqlite-wasm-rs uses a range version (">=0.3.0, <0.4.0")?
  sqlite-wasm-rs may have breaking changes in the future, but this will only happen when a major version is updated.(same as 0.3.0, but more explicit).

• Why "target_family = "wasm", target_os = "unknown""?
  This is a suggestion from rustdoc, see https://doc.rust-lang.org/beta/rustc/platform-support/wasm32-unknown-unknown.html#conditionally-compiling-code for details.

• Why load_extension and unlock_notify features are not supported?
  load_extension requires dlopen support, which is obviously not supported in wasm32-unknown-unknwon.
  wasm is single-threaded (It is actually possible to "multithread", but it is complicated: https://rustwasm.github.io/2018/10/24/multithreading-rust-and-wasm.html), see https://github.com/Spxg/sqlite-wasm-rs?tab=readme-ov-file#about-multithreading for details, so the callback registered with unlock_notify will be executed immediately.

• Why is persistent VFS not provided by default?
  There is no a persistent VFS on the web that can be used by all environments (ui thread, SharedWorker, DedicatedWorker etc.), so memory VFS is provided by default. See https://github.com/Spxg/sqlite-wasm-rs?tab=readme-ov-file#about-vfs for details.

• Why are some tests ignored?
  This is because wasm32-unknown-unknown does not support std::fs and std::time. Fortunately, such test cases are rare and other tests have passed. https://github.com/Spxg/rusqlite/actions/runs/13503535799/job/37727687937

we need to find someone kind enough to validate this PR.

Any suggestions?

Maybe @thomcc or @trevyn ?

It seems like they all don't have time to review it, so I thought of some questions you might be concerned about, I hope this can answer your questions.

@thomcc @gwenn @trevyn any other questions or suggestions?

@gwenn any suggestions? wasm-bindgen was unmaintained for a while, which might have been a concern for you, but the organization has changed and things are moving in a positive direction. wasm-bindgen/wasm-bindgen#4533

Just for reference:
https://blog.rust-lang.org/2025/04/04/c-abi-changes-for-wasm32-unknown-unknown/

Just for reference: https://blog.rust-lang.org/2025/04/04/c-abi-changes-for-wasm32-unknown-unknown/

Yes, wasm32-unknown-unknown is now C-ABI aligned, which means linking to emscripten or wasi will not be a problem.

Just for reference: https://blog.rust-lang.org/2025/04/04/c-abi-changes-for-wasm32-unknown-unknown/

Yes, wasm32-unknown-unknown is now C-ABI aligned, which means linking to emscripten or wasi will not be a problem.

Which means the official sqlite3.wasm ?

Which means the official sqlite3.wasm ?

This means we can compile sqlite3 with emcc and link it into our rust wasm32-unknown-unknown program, just like sqlite-wasm-rs does.

However, this is only one step, more work is actually to implement a persistent VFS under wasm32-unknown-unknown, like opfs: https://github.com/Spxg/sqlite-wasm-rs/blob/master/sqlite-wasm-rs/src/vfs/sahpool.rs

If you are interested, you can try it out at https://sqlight.dev

more work

Of course, another important work is to complete some C functions:
https://github.com/Spxg/sqlite-wasm-rs/blob/master/sqlite-wasm-rs/src/shim.rs

Ok, thanks for the details.