Lines Matching refs:is
3 This is the README for the files `sqlite3-*.js` and
4 `sqlite3-wasm.c`. This collection of files is used to build a
5 single-file distribution of the sqlite3 WASM API. It is broken into
10 OO#1 API is not needed.
19 Note that the structure described here is the current state of things,
22 The overall idea is that the following files get concatenated
23 together, in the listed order, the resulting file is loaded by a
28 objects. This is exposed as a function, rather than objects, so that
36 more portable to arbitrary WASM toolchains. This API is
38 toolchains. It is "semi-third-party" in that it was created in order
39 to support this tree but is standalone and maintained together
44 or C are visible to the other end of the connection. This is also an
53 `sqlite3.version` object. This part is not critical, but records the
57 API, colloquially known as OO API #1. Its API is similar to other
59 to anyone familiar with such APIs. That said, it is not a "required
65 this is an optional component, offering one of any number of
68 Is not part of the amalgamated sources and is intended to be
70 and runs the Worker #1 API which is implemented in
74 a Promise-based interface into the Worker #1 API. This is
78 is an sqlite3 VFS implementation which supports Google Chrome's
82 is the asynchronous backend part of the OPFS proxy. It speaks
85 started in its own Worker, is not part of the amalgamation.
92 process, which is what finally executes the initialization code
99 `sqlite3-api.js`, which is everything except for the `post-js-*.js`
100 files, and `sqlite3.js`, which is the Emscripten-generated amalgamated
104 The non-JS outlier file is `sqlite3-wasm.c`: it is a proxy for
107 to private/static `sqlite3.c` internals. `sqlite3.wasm` is compiled
115 flag. As of this writing, that file is only used for experimentation
119 file is intended as a place to override certain Emscripten behavior
131 `sqlite3InitModule()` function with one which, after the module is