@baukit/data-contracts-expo-sqlite 0.1.0 → 0.1.2

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.
Files changed (2) hide show
  1. package/README.md +11 -1
  2. package/package.json +12 -11
package/README.md CHANGED
@@ -37,7 +37,7 @@ transaction. Independent root calls are serialized. `close()` closes the
37
37
  logical adapter; pass `{ closeDatabase: true }` when it should also own the
38
38
  supplied database handle.
39
39
 
40
- Namespaces share one fixed `baukit_records` table without colliding. Call `initialize()` before using a store. Records are serialized as JSON, pagination is bounded and keyset-based, and malformed persisted payloads produce a content-free error. The package does not choose a database name, open a singleton, define product entities, or implement product cache policy.
40
+ Namespaces share one fixed `baukit_records` table without colliding. Call `initialize()` before using a store. Records are serialized as JSON, pagination is bounded and keyset-based, and malformed persisted payloads produce a content-free error.
41
41
 
42
42
  The package's fast Vitest suite uses a deterministic database fake. The
43
43
  [Expo SQLite device-conformance app](../../../examples/expo-sqlite-conformance/README.md)
@@ -46,3 +46,13 @@ including creation/reopening, namespace isolation, malformed data, rollback,
46
46
  schema-metadata upgrades, and authenticated E→F→E database isolation. Products
47
47
  derive the database name and resolve its registry with `@baukit/data-contracts`
48
48
  before opening the Expo database. iOS is a scheduled/manual macOS gate.
49
+
50
+ ## Boundaries
51
+
52
+ The package implements `@baukit/data-contracts` on Expo SQLite and nothing else. It does not choose a
53
+ database name, open a singleton, define product entities, or implement cache policy.
54
+
55
+ Passing the database handle in rather than opening one is what makes an authenticated product able to
56
+ derive its database name per identity, which is what the shared E→F→E isolation cases exercise.
57
+
58
+ `@baukit/data-contracts-dexie` is the same contract on the web.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@baukit/data-contracts-expo-sqlite",
3
- "version": "0.1.0",
3
+ "version": "0.1.2",
4
4
  "description": "Expo SQLite implementation of the @baukit/data-contracts base storage contracts.",
5
5
  "license": "MIT",
6
6
  "author": "Patrick Koss",
@@ -32,19 +32,20 @@
32
32
  "README.md",
33
33
  "LICENSE"
34
34
  ],
35
- "devDependencies": {
36
- "expo-sqlite": "57.0.1",
37
- "typescript": "6.0.3",
38
- "@baukit/data-contracts": "0.1.0"
39
- },
40
- "peerDependencies": {
41
- "@baukit/data-contracts": "^0.1.0",
42
- "expo-sqlite": "^57.0.1"
43
- },
44
35
  "scripts": {
45
36
  "build": "tsc -p tsconfig.json",
37
+ "prepare": "pnpm run build",
46
38
  "test": "vitest run --config ../../vitest.config.ts",
47
39
  "lint": "eslint src --max-warnings=0",
48
40
  "format:check": "prettier --check src package.json tsconfig.json"
41
+ },
42
+ "devDependencies": {
43
+ "@baukit/data-contracts": "workspace:*",
44
+ "expo-sqlite": "57.0.1",
45
+ "typescript": "6.0.3"
46
+ },
47
+ "peerDependencies": {
48
+ "@baukit/data-contracts": "^0.1.2",
49
+ "expo-sqlite": "^57.0.1"
49
50
  }
50
- }
51
+ }