@statewalker/db-duckdb-browser 0.1.7 → 0.1.8
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +0 -5
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -7,11 +7,6 @@ A DuckDB driver for the browser that implements `Db` from
|
|
|
7
7
|
Worker. The database lives in memory, or in an OPFS file that survives page
|
|
8
8
|
reloads.
|
|
9
9
|
|
|
10
|
-
> **Known issue:** with `@duckdb/duckdb-wasm` 1.33.1-dev57.0, a new OPFS database is not
|
|
11
|
-
> actually written to OPFS, so it does not survive a reopen
|
|
12
|
-
> ([#74](https://github.com/statewalker/statewalker-db/issues/74)). The persistence tests in
|
|
13
|
-
> `src/opfs-persistence.browser.test.ts` are marked as expected failures until that is fixed.
|
|
14
|
-
|
|
15
10
|
## Why it exists
|
|
16
11
|
|
|
17
12
|
DuckDB WASM has its own asynchronous API built around Arrow tables, worker
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@statewalker/db-duckdb-browser",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.8",
|
|
4
4
|
"private": false,
|
|
5
5
|
"type": "module",
|
|
6
6
|
"description": "DuckDB WASM driver for @statewalker/db-api, targeting browser environments.",
|
|
@@ -33,7 +33,7 @@
|
|
|
33
33
|
"!src/**/test-wasm-node.ts"
|
|
34
34
|
],
|
|
35
35
|
"dependencies": {
|
|
36
|
-
"@duckdb/duckdb-wasm": "
|
|
36
|
+
"@duckdb/duckdb-wasm": "1.33.1-dev65.0",
|
|
37
37
|
"@statewalker/db-api": "^0.1.6"
|
|
38
38
|
},
|
|
39
39
|
"devDependencies": {
|