Rework the Emscripten-emitted module loader/init function such that it passes on the sqlite3 module, instead of the Emscripten module, to the first then() of sqlite3InitModule()'s returned Promise. This eliminates any need to mention the Emscripten module object in client-side code unless they want to configure it in advance for loading-status reports.

FossilOrigin-Name: 0dbaa0e2b5abf5c23e2039ec90a3055ebb3c063aaf4e556c42546defe6fbb86d

1 files changed, 1 insertions, 3 deletions

diff --git a/ext/wasm/common/SqliteTestUtil.js b/ext/wasm/common/SqliteTestUtil.js
index 277ab5529..08688fd48 100644
--- a/ext/wasm/common/SqliteTestUtil.js
+++ b/ext/wasm/common/SqliteTestUtil.js
@@ -230,9 +230,7 @@
        object, calls it sqlite3InitModule(), and removes
        self.sqlite3ApiConfig after initialization is done. Returns the
        promise from sqlite3InitModule(), and the next then() handler
-       will get the Emscripten module object as its argument. That
-       module has the sqlite3's main namespace object installed as its
-       `sqlite3` property.
+       will get the sqlite3 API object as its argument.
     */
     initSqlite3: function(){
       self.sqlite3ApiConfig = this.sqlite3ApiConfig;