snapback4-expo 0.1.14 → 0.2.0

package/README.md

@@ -2,18 +2,27 @@
 
 Snapback 4's device in Rust, as an Expo module: the partition in its own
 SQLite, the stream applied, the outbox kept, queries and predictions
-answered — the same interpreter the server runs — behind one JSON call.
-`snapback4/native` is the client over it:
+answered — the same interpreter the server runs, and the same module the
+web runs as wasm — behind one JSON call. `snapback4/local` is the client
+over it:
 
 ```ts
-import { createNativeClient } from "snapback4/native";
-import { nativeAvailable, nativeDevice, documentDirectory } from "snapback4-expo";
+import { createLocalClient } from "snapback4/local";
+import { createClient } from "snapback4/client";
+import { nativeAvailable, nativeDevice } from "snapback4-expo";
 
+const safe = (name: string) => name.replace(/[^A-Za-z0-9._-]/g, "_");   // store and session names carry the URL and the viewer
+const sqliteStore = { open: async (name: string, schema: unknown) => openSqlite(expoSqliteDriver(await SQLite.openDatabaseAsync(`${safe(name)}.db`)), schema) };
 const client = nativeAvailable()
-  ? await createNativeClient({ url, guest: true, sessionStore, native: nativeDevice, dataDir: documentDirectory() })
-  : await createLocalClient({ url, guest: true, sessionStore, store: sqliteStore });   // Expo Go: the TypeScript tier
+  ? await createLocalClient({ url, guest: true, sessionStore, device: nativeDevice })
+  : createClient({ url, session });   // Expo Go: the online tier, with a session the app keeps
 ```
 
+`createNativeClient` probes the module first and rejects with
+`E_NATIVE_VERSION` when the native binary predates the JavaScript client:
+reloading JavaScript does not update the module; rebuild the development
+build.
+
 Expo Go loads no custom native code, so the module is present only in a
 development or production build: add `expo-dev-client`, then
 `npx expo run:ios` (the module autolinks; nothing to configure). The

package/ios/Snapback4Device.xcframework/Info.plist

@@ -10,7 +10,7 @@
 			<key>HeadersPath</key>
 			<string>Headers</string>
 			<key>LibraryIdentifier</key>
-			<string>ios-arm64-simulator</string>
+			<string>ios-arm64</string>
 			<key>LibraryPath</key>
 			<string>libsnapback4_device.a</string>
 			<key>SupportedArchitectures</key>
@@ -19,8 +19,6 @@
 			</array>
 			<key>SupportedPlatform</key>
 			<string>ios</string>
-			<key>SupportedPlatformVariant</key>
-			<string>simulator</string>
 		</dict>
 		<dict>
 			<key>BinaryPath</key>
@@ -28,7 +26,7 @@
 			<key>HeadersPath</key>
 			<string>Headers</string>
 			<key>LibraryIdentifier</key>
-			<string>ios-arm64</string>
+			<string>ios-arm64-simulator</string>
 			<key>LibraryPath</key>
 			<string>libsnapback4_device.a</string>
 			<key>SupportedArchitectures</key>
@@ -37,6 +35,8 @@
 			</array>
 			<key>SupportedPlatform</key>
 			<string>ios</string>
+			<key>SupportedPlatformVariant</key>
+			<string>simulator</string>
 		</dict>
 	</array>
 	<key>CFBundlePackageType</key>

package/package.json

@@ -1,11 +1,16 @@
 {
   "name": "snapback4-expo",
-  "version": "0.1.14",
+  "version": "0.2.0",
   "type": "module",
   "description": "Snapback 4's native module for Expo: the device in Rust (the partition in its own SQLite, the stream applied, the outbox kept, queries and predictions answered) behind one JSON call, and the opener `snapback4/native` takes.",
   "main": "src/index.ts",
   "types": "src/index.ts",
-  "files": ["src", "ios", "expo-module.config.json", "README.md"],
+  "files": [
+    "src",
+    "ios",
+    "expo-module.config.json",
+    "README.md"
+  ],
   "peerDependencies": {
     "expo": "*",
     "snapback4": "*"

package/src/index.ts

@@ -1,9 +1,9 @@
-// The opener `snapback4/native` takes, over the Expo module: absent in
+// The opener `snapback4/local` takes, over the Expo module: absent in
 // Expo Go (which loads no custom native code), present in a development
-// or production build. An app asks `nativeAvailable()` and falls back to
-// the TypeScript tier (`snapback4/local` over expo-sqlite) when it is not.
+// or production build. An app asks `nativeAvailable()` and runs the
+// online tier (`snapback4/client`) when it is not.
 import { requireOptionalNativeModule } from "expo-modules-core";
-import type { NativeCore, NativeOpener } from "snapback4/native";
+import type { DeviceCore, DeviceOpener } from "snapback4/local";
 
 interface Snapback4Native {
   readonly documentDirectory: string;
@@ -26,10 +26,10 @@ export function documentDirectory(): string {
   return native.documentDirectory;
 }
 
-export const nativeDevice: NativeOpener = {
-  async open(path, backend): Promise<NativeCore> {
+export const nativeDevice: DeviceOpener = {
+  async open(name, backend): Promise<DeviceCore> {
     if (!native) throw new Error("snapback4-expo: the native module is not in this build (Expo Go loads no custom native code; make a development build)");
-    const handle = await native.open(path, backend ? JSON.stringify(backend) : null);
+    const handle = await native.open(`${native.documentDirectory.replace(/\/$/, "")}/${name}.sqlite`, backend ? JSON.stringify(backend) : null);
     return {
       async call(request) {
         const t0 = trace ? Date.now() : 0;