dart2wasm support

[simolus3]

Current state: package:sqlite3 experimentally supports being compiled with dart2wasm. Unit tests exercising the bindings themselves all pass, but persistence is broken. There are additional caveats and todos to be aware of:

• (fixed in upcoming Dart SDK release) dart2wasm doesn't seem to support Random.secure(), which we use for our VFS implementations. You can work around this issue by supplying your own non-secure Random() instance to VFS constructors, but please be aware that this may be a security risk. sqlite3 docs require that "The xRandomness() function attempts to return nBytes bytes of good-quality randomness into zOut", so I won't use the non-secure random instance as a default in this package.
• When binding over web APIs returning JavaScript ArrayBuffers, we're converting them to Dart TypedData subclasses for convenience. This is not sound for dart2wasm, which copies the bytes instead of referencing the original buffer. This may just be hugely inefficient, but it can also cause deadlocks for OPFS and data corruption issues on other VFS implementations.
• We're currently loading an additional wasm module for sqlite3 (sqlite3.wasm). Once the native assets feature is stable and supports WebAssembly, obviously we want to link the Dart application and sqlite3 into the same wasm file for easier deployments.

[ekuleshov]

For secure rng. Could you use one of the implementations from the pointycastle package?

[simolus3]

That doesn't help getting entropy. Secure random has been implemented, it's just not on stable yet. So we can just wait.

[JamesMcIntosh]

Where are things at now with sqlite3.wasm?

[simolus3]

This issue is about using the sqlite3 package with dart2wasm-compiled apps. I believe that should mostly just work at this point. Especially when using drift or the sqlite3_web package relying on a web worker, it really doesn't make much of a difference whether dart2js or dart2wasm is used. I think I have some documentation to update, but we run integration tests with both compilers so you can expect that to work.

[simolus3]

Oh, I now see you probably meant the last point from the issue description right? Linking Dart and other wasm modules still not really feasible in Dart at the moment.