@koolbase/react-native 10.0.1 → 10.2.0

package/CHANGELOG.md

@@ -7,6 +7,31 @@ adheres to [Semantic Versioning][semver].
 [kac]: https://keepachangelog.com/en/1.1.0/
 [semver]: https://semver.org/
 
+## 10.2.0
+
+### Changed
+
+- The platform seam gains a locking contract. React Native satisfies it by
+  running the function: one process, one store, nothing to coordinate.
+
+## 10.1.0
+
+### Changed
+
+- `UploadOptions.file` accepts a `Blob` in addition to `{ uri, name, type }`.
+  The React Native path is unchanged; the union exists because the same core
+  now serves a browser, where a `File` is the only form the bytes come in.
+
+## 10.0.2
+
+### Fixed
+
+- **A Node process that initialized the SDK never exited.** The analytics
+  flush interval, and a pending realtime reconnect, counted as work on Node's
+  event loop, so a CLI, a test runner or an SSR build step hung after its last
+  line. Both timers are now unref'd where the runtime supports it. A browser
+  is unaffected: the page keeps itself alive regardless.
+
 ## 10.0.1
 
 No changes to this package. Released to keep the version aligned with

package/dist/cjs/platform.js

@@ -38,6 +38,13 @@ function reactNativePlatform() {
             os: String(react_native_1.Platform.OS),
             version: String(react_native_1.Platform.Version),
         },
+        // A React Native app is one process over its own storage. Two copies of
+        // the SDK cannot be racing over one AsyncStorage, so the in-process
+        // serialisation in offline-state is the whole answer.
+        locks: {
+            exclusive: (_name, fn) => fn(),
+            tryExclusive: async (_name, fn) => { await fn(); return { ran: true }; },
+        },
         authStorage: () => ((0, auth_storage_js_1.isKeychainAvailable)() ? new auth_storage_js_1.SecureAuthStorage() : null),
     };
 }

package/dist/esm/platform.js

@@ -32,6 +32,13 @@ export function reactNativePlatform() {
             os: String(Platform.OS),
             version: String(Platform.Version),
         },
+        // A React Native app is one process over its own storage. Two copies of
+        // the SDK cannot be racing over one AsyncStorage, so the in-process
+        // serialisation in offline-state is the whole answer.
+        locks: {
+            exclusive: (_name, fn) => fn(),
+            tryExclusive: async (_name, fn) => { await fn(); return { ran: true }; },
+        },
         authStorage: () => (isKeychainAvailable() ? new SecureAuthStorage() : null),
     };
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@koolbase/react-native",
-  "version": "10.0.1",
+  "version": "10.2.0",
   "description": "React Native SDK for Koolbase \u2014 auth, database, storage, realtime, feature flags, and functions in one package.",
   "main": "./dist/cjs/index.js",
   "types": "./dist/esm/index.d.ts",
@@ -24,7 +24,7 @@
     "url": "https://github.com/koolbase/koolbase-react-native"
   },
   "dependencies": {
-    "@koolbase/core": "10.0.1"
+    "@koolbase/core": "10.2.0"
   },
   "peerDependencies": {
     "@react-native-async-storage/async-storage": "^3.0.2",