From 1fc6ffccc55fc7105ce9426149e63446e062c01f Mon Sep 17 00:00:00 2001 From: stephan Date: Sun, 30 Oct 2022 09:47:33 +0000 Subject: Minor WASM build cleanups. Enable custom Module.instantiateWasm() when not in WASMFS mode (where it doesn't work). Add sqlite3.debugModule URL param to enable some module-init-time debugging output. FossilOrigin-Name: 50f678846a2b3c3d0818f0bae89f2ee86252a2e6a9c7029ebaae3953ca0fa14c --- ext/wasm/api/post-js-header.js | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'ext/wasm/api/post-js-header.js') diff --git a/ext/wasm/api/post-js-header.js b/ext/wasm/api/post-js-header.js index f377a6541..82a80e5a1 100644 --- a/ext/wasm/api/post-js-header.js +++ b/ext/wasm/api/post-js-header.js @@ -5,7 +5,7 @@ environment must have been set up already but it will not have loaded its WASM when the code in this file is run. The function it installs will be run after the WASM module is loaded, at which - point the sqlite3 WASM API bits will be set up. + point the sqlite3 JS API bits will get set up. */ if(!Module.postRun) Module.postRun = []; Module.postRun.push(function(Module/*the Emscripten-style module object*/){ -- cgit v1.2.3