en Copyright 2015 Java http://172.16.0.5:8080/history/sqlite-3.40.0/ext/wasm/test-opfs-vfs.html#cd0df83c Apply considerable acrobatics to get the JS/WASM deliverables building to and loadable from a directory other than the one which contains the app-level code. Requires an only-slightly-leaky abstraction of passing a URL argument when loading sqlite3.js but provides much greater flexibility in where the JS/WASM files are located.FossilOrigin-Name: 6d468dab9eb84d4548f68014959f02fe4f66455472ff24fe729382bb2972e3d1 List of files: /sqlite-3.40.0/ext/wasm/test-opfs-vfs.html Wed, 19 Oct 2022 04:44:58 +0000 stephan <stephan@noemail.net> http://172.16.0.5:8080/history/sqlite-3.40.0/ext/wasm/test-opfs-vfs.html#f3860120 Numerous cleanups in the JS bits. Removed some now-defunct wasm test files. Expose sqlite3.opfs object containing various OPFS-specific utilities.FossilOrigin-Name: 26e625d05d9820033b23536f18ad3ddc59ed712ad507d4b0c7fe88abd15d2be8 List of files: /sqlite-3.40.0/ext/wasm/test-opfs-vfs.html Sun, 18 Sep 2022 17:32:35 +0000 stephan <stephan@noemail.net> http://172.16.0.5:8080/history/sqlite-3.40.0/ext/wasm/test-opfs-vfs.html#0db30895 Move the OPFS VFS bits back into api/sqlite3-api-opfs.js. Refactor the OPFS VFS init process to use a Promise-returning function which the client must call, as that eliminates any uncertainty about when the VFS (necessarily activated asynchronously) actually becomes available to the client. Rename x-sync-async.* to test-opfs-vfs.* Milestone: first successful test of OPFS without WASMFS.FossilOrigin-Name: b2abf60dbfa6648f671a3932cb65feb28d05a0d5b7f792351d14f9c13d9798c5 List of files: /sqlite-3.40.0/ext/wasm/test-opfs-vfs.html Sun, 18 Sep 2022 03:05:55 +0000 stephan <stephan@noemail.net>