Rename several demo/test files and include more of them in the end-user dist archive.

FossilOrigin-Name: 9c85835f6f50eb3b1a2b89c817816335743f04440c48bfa05aa89ec519cc0d51

ext/wasm/api/sqlite3-api-worker1.js

@@ -106,7 +106,7 @@
 
   ```
   {
-    type: 'error',
+    type: "error",
 
     messageId: ...as above...,
 
@@ -150,7 +150,7 @@
 
   ```
   {
-    type: 'config',
+    type: "config-get",
     messageId: ...as above...,
     result: {
 
@@ -167,7 +167,7 @@
       the non-WASMFS OPFS VFS to open a database via a URI-style
       db filename.
 
-      vfses: result of sqlite3.capi.sqlite3_web_vfs_list()
+      vfsList: result of sqlite3.capi.sqlite3_web_vfs_list()
    }
   }
   ```
@@ -196,7 +196,7 @@
 
   ```
   {
-    type: 'open',
+    type: "open",
     messageId: ...as above...,
     result: {
       filename: db filename, possibly differing from the input.
@@ -205,7 +205,7 @@
       envelope to other calls in this API to tell them which db to
       use. If it is not provided to future calls, they will default to
       operating on the first-opened db. This property is, for API
-      consistency's sake, also part of the contaning message envelope.
+      consistency's sake, also part of the containing message envelope.
       Only the `open` operation includes it in the `result` property.
 
       persistent: true if the given filename resides in the
@@ -237,7 +237,7 @@
 
   ```
   {
-    type: 'close',
+    type: "close",
     messageId: ...as above...,
     result: {
 
@@ -269,7 +269,7 @@
 
   ```
   {
-    type: 'exec',
+    type: "exec",
     messageId: ...as above...,
     dbId: ...as above...
     result: {
@@ -370,8 +370,7 @@ sqlite3.initWorker1API = function(){
         if(alsoUnlink && filename){
           /* This isn't necessarily correct: the db might be using a
              VFS other than the default. How do we best resolve this
-             without having to special-case the kvvfs and opfs
-             VFSes? */
+             without having to special-case the opfs VFSes? */
           sqlite3.capi.wasm.sqlite3_wasm_vfs_unlink(filename);
         }
       }
@@ -524,7 +523,7 @@ sqlite3.initWorker1API = function(){
       });
       rc.wasmfsOpfsEnabled = !!sqlite3.capi.sqlite3_wasmfs_opfs_dir();
       rc.version = sqlite3.version;
-      rc.vfses = sqlite3.capi.sqlite3_web_vfs_list();
+      rc.vfsList = sqlite3.capi.sqlite3_web_vfs_list();
       return rc;
     },
 

ext/wasm/api/sqlite3-worker1-promiser.js

@@ -70,8 +70,8 @@
    message. The second expects an object in the form {type:...,
    args:...}  plus any other properties the client cares to set. This
    function will always set the `messageId` property on the object,
-   even if it's already set, and will set the `dbId` property to
-   `config.dbId` if it is _not_ set in the message object.
+   even if it's already set, and will set the `dbId` property to the
+   current database ID if it is _not_ set in the message object.
 
    The function throws on error.
 

ext/wasm/api/sqlite3-worker1.js

@@ -26,11 +26,8 @@
   Worker constructor and then listen for an event in the form shown
   above in order to know when the module has completed initialization.
 
-  This file accepts a couple of URL arguments to adjust how it loads
-  sqlite3.js:
+  This file accepts a URL arguments to adjust how it loads sqlite3.js:
 
-  - `sqlite3.js`, if set, is used as the URI to `sqlite3.js` and it
-    may contain path elements, e.g. `sqlite3.js=foo/bar/my-sqlite3.js`.
   - `sqlite3.dir`, if set, treats the given directory name as the
     directory from which `sqlite3.js` will be loaded.
 
@@ -40,9 +37,7 @@
 (()=>{
   const urlParams = new URL(self.location.href).searchParams;
   let theJs = 'sqlite3.js';
-  if(urlParams.has('sqlite3.js')){
-    theJs = urlParams.get('sqlite3.js');
-  }else if(urlParams.has('sqlite3.dir')){
+  if(urlParams.has('sqlite3.dir')){
     theJs = urlParams.get('sqlite3.dir') + '/' + theJs;
   }
   importScripts(theJs);