https://www.sqlite.org/json1.html

…479)

* Run `npm ci` automatically after the devcontainer is created.
This reduces the chance that another dev will forget to do this.

* Upgrade to Emscripten 2.0.29
Changes required:
* Defined EM_NODE_JS environment variable to get rid of
a warning that appears if the NODE environment variable
is set, but EM_NODE_JS is not.
* EXTRA_EXPORTED_RUNTIME_METHODS is now EXPORTED_RUNTIME_METHODS
* No longer pass the `-s LINKABLE=1` option to emcc when compiling. (This is a linktime setting and emcc
warns about not using a linktime setting when compiling now).

* Upgrade to Sqlite 3.36.0
Sqlite now publishes the hash as a SHA3 instead of SHA1,
necessitating the installation of the sha3sum command.

* Use -Oz optimizations instead of -O2
This reduces most compilation output by around 50%

* Upgrade to Emscripten 3.0.0

* Upgrade to sqlite 3.38.5

Fixes #510

`Buffer()` is deprecated due to security and usability issues

Changed "Is is generated..." to "It is generated...".

* Run `npm ci` automatically after the devcontainer is created.
This reduces the chance that another dev will forget to do this.

* Upgrade to Emscripten 2.0.29
Changes required:
* Defined EM_NODE_JS environment variable to get rid of
a warning that appears if the NODE environment variable
is set, but EM_NODE_JS is not.
* EXTRA_EXPORTED_RUNTIME_METHODS is now EXPORTED_RUNTIME_METHODS
* No longer pass the `-s LINKABLE=1` option to emcc when compiling. (This is a linktime setting and emcc
warns about not using a linktime setting when compiling now).

This reduces the chance that another dev will forget to do this.

* Run `npm ci` automatically after the devcontainer is created.
This reduces the chance that another dev will forget to do this.

* Upgrade to Emscripten 2.0.29
Changes required:
* Defined EM_NODE_JS environment variable to get rid of
a warning that appears if the NODE environment variable
is set, but EM_NODE_JS is not.
* EXTRA_EXPORTED_RUNTIME_METHODS is now EXPORTED_RUNTIME_METHODS
* No longer pass the `-s LINKABLE=1` option to emcc when compiling. (This is a linktime setting and emcc
warns about not using a linktime setting when compiling now).

* Upgrade to Sqlite 3.36.0
Sqlite now publishes the hash as a SHA3 instead of SHA1,
necessitating the installation of the sha3sum command.

* README: fix broken contributing link

* CONTRIBUTING: fix numbered list

…d-rejections=strict to npm tests. (#472)

…445)

* Initial default .devcontainer and Dockerfile created

* Install EMSDK and Chrome dependencies in the Dockerfile

* Move Contributing/Compiling instructions to Contributing.md

* Start worker test in Puppeteer without Chrome sandbox when running in Docker

* Add `clean` package script and express `rebuild` script in terms of npm scripts

This aims to express all build tasks via npm scripts via make commands, rather than expressing some scripts as npm scripts and others in terms of make.

* Pin EMSDK to 2.0.15

* First attempt at Github action building inside of Docker container

* Switch cmd to entrypoint

* Create an entrypoint.sh for the Github build-sqljs action

* remove comments

* Make action script executable

* Set correct path in docker image

Co-authored-by: lovasoa <pere.jobs@gmail.com>

* Added partial BigInt support

Moved from es6 to support bigint

Changed from getNumber to getBigInt

Avoided blobal redeclaration of function/variables

Improved BigInt support, handled bind params for bigInt

Logical change on how big int is supported

BigInt is not fully supported at WASM level

Added config to enable and disable bigInt support

Added documentation

Changed var to const as per readme standard

* Changes as per PR comments

* Changes as per PR comments - future extension support

Replace `var` with `const` in the code example in README.
`const` is better, and since `const` and `var` were mixed up, I unified them into `const`.

Just a small error.

Bumps [hosted-git-info](https://github.com/npm/hosted-git-info) from 2.8.8 to 2.8.9.
- [Release notes](https://github.com/npm/hosted-git-info/releases)
- [Changelog](https://github.com/npm/hosted-git-info/blob/v2.8.9/CHANGELOG.md)
- [Commits](npm/hosted-git-info@v2.8.8...v2.8.9)

Signed-off-by: dependabot[bot] <support@github.com>

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Bumps [lodash](https://github.com/lodash/lodash) from 4.17.19 to 4.17.21.
- [Release notes](https://github.com/lodash/lodash/releases)
- [Commits](lodash/lodash@4.17.19...4.17.21)

Signed-off-by: dependabot[bot] <support@github.com>

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

The dependencies/ordering of the building of the .bc files were subtly incorrect. This meant that running `make clean` followed by `make build` would work, but then the next time `make build` was run, the whole build would erroneously run again, rather than detecting everything was up to date.

In particular, the 'out/sqlite3.bc' file would get built, and THEN the extensions would get built. However, when the extensions got built, only then would it copy the extensions.c file into the sqlite-src/amalgamation folder, thus updating that the sqlite-src/amalgamation folder timestamp. The next time `make` was run, `out/sqlite3.bc` would detect that the `sqlite-src/amalgamation` folder was newer than the sqlite3.bc file, and it would get rebuilt, thus cascading into a full rebuild.