@koolbase/js 10.2.0 → 10.4.0

package/CHANGELOG.md

@@ -7,6 +7,44 @@ is based on [Keep a Changelog][kac], and this project adheres to
 [kac]: https://keepachangelog.com/en/1.1.0/
 [semver]: https://semver.org/
 
+## 10.4.0
+
+### Added
+
+- **`auth.verifyEmail(token)`** — complete email verification with a token
+  from a verification link. The endpoint and the Flutter SDK have had this;
+  the TypeScript SDKs did not, so an app's verify-email page had nothing to
+  call.
+
+- **`auth.resendVerificationEmail()`** — re-send the verification email to a
+  signed-in but unverified user. Returns `{ alreadyVerified, expiresAt,
+  cooldownUntil }`; an already-verified account is a no-op that says so
+  rather than an error, which is what a resend button needs when the user
+  verified in another tab.
+
+  The server throttles this, and the refusal now arrives typed:
+  `VerificationResendCooldownError` carries `cooldownUntil` so you can show a
+  countdown, and `VerificationResendDailyCapError` is separate because the
+  remedy differs — wait seconds versus wait until tomorrow.
+
+## 10.3.0
+
+### Fixed
+
+- **Analytics events carried no user unless the app called `identify()`.**
+  Nothing errored when it never did, so every event landed anonymous and
+  retention, funnels and per-user analysis were quietly worthless — found in
+  a real project as 53 events, 8 registered users, and not one event carrying
+  a user id. The SDK already knows who is signed in; it now says so. The
+  Flutter SDK fixed this in 11.2.0 and the TypeScript SDKs did not, until now.
+
+  `identify()` still wins for an app with its own identity system, and
+  `reset()` releases that override and falls back to the Koolbase session.
+
+  If you have been calling `identify()` yourself, nothing changes. If you have
+  not, your events will start carrying users — which is the point, though it
+  means your analytics before and after this version are not comparable.
+
 ## 10.2.0
 
 ### Added

package/dist/cjs/index.js

@@ -38,6 +38,15 @@ let _functions = null;
 let _flags = null;
 let _analytics = null;
 let _initialized = false;
+// The in-flight initialize, so overlapping callers await the same one.
+//
+// A boolean guard is not enough: the check happens before the first await
+// and the flag is set after the last, so two calls that overlap in that
+// window both pass and both build a whole SDK — two of every client, two
+// analytics flush timers, two sync engines over one queue. React strict
+// mode does exactly this in development, and so does any app that
+// initializes from two components.
+let _initializing = null;
 function ensureInitialized() {
     if (!_initialized) {
         throw new Error('Koolbase not initialized. Call Koolbase.initialize(config) first.');
@@ -47,19 +56,31 @@ exports.Koolbase = {
     async initialize(config) {
         if (_initialized)
             return;
-        (0, core_1.setPlatform)(config.platform ?? (0, platform_js_2.browserPlatform)());
-        _auth = new core_1.KoolbaseAuth(config);
-        _db = new core_1.KoolbaseDatabase(config, () => _auth?.currentUser?.id ?? null, () => _auth?.validAccessToken() ?? Promise.resolve(null), async () => { await _auth?.clearStoredSession(); });
-        _storage = new core_1.KoolbaseStorage(config, () => _auth?.validAccessToken() ?? Promise.resolve(null), async () => { await _auth?.clearStoredSession(); });
-        _realtime = new core_1.KoolbaseRealtime(config, () => _auth?.validAccessToken() ?? Promise.resolve(null), () => _auth?.currentUser?.id ?? null);
-        _functions = new core_1.KoolbaseFunctions(config, () => _auth?.validAccessToken() ?? Promise.resolve(null), async () => { await _auth?.clearStoredSession(); });
-        const deviceId = await (0, core_1.getOrCreateDeviceId)();
-        _flags = new core_1.KoolbaseFlags(config, deviceId);
-        if (config.analyticsEnabled !== false) {
-            _analytics = new core_1.KoolbaseAnalytics(config);
-            await _analytics.init(config.appVersion);
+        if (_initializing)
+            return _initializing;
+        _initializing = (async () => {
+            (0, core_1.setPlatform)(config.platform ?? (0, platform_js_2.browserPlatform)());
+            _auth = new core_1.KoolbaseAuth(config);
+            _db = new core_1.KoolbaseDatabase(config, () => _auth?.currentUser?.id ?? null, () => _auth?.validAccessToken() ?? Promise.resolve(null), async () => { await _auth?.clearStoredSession(); });
+            _storage = new core_1.KoolbaseStorage(config, () => _auth?.validAccessToken() ?? Promise.resolve(null), async () => { await _auth?.clearStoredSession(); });
+            _realtime = new core_1.KoolbaseRealtime(config, () => _auth?.validAccessToken() ?? Promise.resolve(null), () => _auth?.currentUser?.id ?? null);
+            _functions = new core_1.KoolbaseFunctions(config, () => _auth?.validAccessToken() ?? Promise.resolve(null), async () => { await _auth?.clearStoredSession(); });
+            const deviceId = await (0, core_1.getOrCreateDeviceId)();
+            _flags = new core_1.KoolbaseFlags(config, deviceId);
+            if (config.analyticsEnabled !== false) {
+                _analytics = new core_1.KoolbaseAnalytics(config, () => _auth?.currentUser?.id ?? null);
+                await _analytics.init(config.appVersion);
+            }
+            _initialized = true;
+        })();
+        try {
+            await _initializing;
+        }
+        finally {
+            // Cleared either way: a failed initialize must be retryable rather
+            // than leaving every later caller awaiting a rejected promise.
+            _initializing = null;
         }
-        _initialized = true;
     },
     get auth() { ensureInitialized(); return _auth; },
     get db() { ensureInitialized(); return _db; },

package/dist/esm/index.js

@@ -19,6 +19,15 @@ let _functions = null;
 let _flags = null;
 let _analytics = null;
 let _initialized = false;
+// The in-flight initialize, so overlapping callers await the same one.
+//
+// A boolean guard is not enough: the check happens before the first await
+// and the flag is set after the last, so two calls that overlap in that
+// window both pass and both build a whole SDK — two of every client, two
+// analytics flush timers, two sync engines over one queue. React strict
+// mode does exactly this in development, and so does any app that
+// initializes from two components.
+let _initializing = null;
 function ensureInitialized() {
     if (!_initialized) {
         throw new Error('Koolbase not initialized. Call Koolbase.initialize(config) first.');
@@ -28,19 +37,31 @@ export const Koolbase = {
     async initialize(config) {
         if (_initialized)
             return;
-        setPlatform(config.platform ?? browserPlatform());
-        _auth = new KoolbaseAuth(config);
-        _db = new KoolbaseDatabase(config, () => _auth?.currentUser?.id ?? null, () => _auth?.validAccessToken() ?? Promise.resolve(null), async () => { await _auth?.clearStoredSession(); });
-        _storage = new KoolbaseStorage(config, () => _auth?.validAccessToken() ?? Promise.resolve(null), async () => { await _auth?.clearStoredSession(); });
-        _realtime = new KoolbaseRealtime(config, () => _auth?.validAccessToken() ?? Promise.resolve(null), () => _auth?.currentUser?.id ?? null);
-        _functions = new KoolbaseFunctions(config, () => _auth?.validAccessToken() ?? Promise.resolve(null), async () => { await _auth?.clearStoredSession(); });
-        const deviceId = await getOrCreateDeviceId();
-        _flags = new KoolbaseFlags(config, deviceId);
-        if (config.analyticsEnabled !== false) {
-            _analytics = new KoolbaseAnalytics(config);
-            await _analytics.init(config.appVersion);
+        if (_initializing)
+            return _initializing;
+        _initializing = (async () => {
+            setPlatform(config.platform ?? browserPlatform());
+            _auth = new KoolbaseAuth(config);
+            _db = new KoolbaseDatabase(config, () => _auth?.currentUser?.id ?? null, () => _auth?.validAccessToken() ?? Promise.resolve(null), async () => { await _auth?.clearStoredSession(); });
+            _storage = new KoolbaseStorage(config, () => _auth?.validAccessToken() ?? Promise.resolve(null), async () => { await _auth?.clearStoredSession(); });
+            _realtime = new KoolbaseRealtime(config, () => _auth?.validAccessToken() ?? Promise.resolve(null), () => _auth?.currentUser?.id ?? null);
+            _functions = new KoolbaseFunctions(config, () => _auth?.validAccessToken() ?? Promise.resolve(null), async () => { await _auth?.clearStoredSession(); });
+            const deviceId = await getOrCreateDeviceId();
+            _flags = new KoolbaseFlags(config, deviceId);
+            if (config.analyticsEnabled !== false) {
+                _analytics = new KoolbaseAnalytics(config, () => _auth?.currentUser?.id ?? null);
+                await _analytics.init(config.appVersion);
+            }
+            _initialized = true;
+        })();
+        try {
+            await _initializing;
+        }
+        finally {
+            // Cleared either way: a failed initialize must be retryable rather
+            // than leaving every later caller awaiting a rejected promise.
+            _initializing = null;
         }
-        _initialized = true;
     },
     get auth() { ensureInitialized(); return _auth; },
     get db() { ensureInitialized(); return _db; },

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@koolbase/js",
-  "version": "10.2.0",
+  "version": "10.4.0",
   "description": "Koolbase SDK for the browser \u2014 auth, database, storage, realtime, functions, flags and offline sync in one package.",
   "main": "./dist/cjs/index.js",
   "types": "./dist/esm/index.d.ts",
@@ -25,7 +25,7 @@
     "url": "https://github.com/koolbase/koolbase-react-native"
   },
   "dependencies": {
-    "@koolbase/core": "10.2.0"
+    "@koolbase/core": "10.4.0"
   },
   "publishConfig": {
     "access": "public"