@koolbase/js 10.3.0 → 11.0.0

package/CHANGELOG.md

@@ -7,6 +7,86 @@ is based on [Keep a Changelog][kac], and this project adheres to
 [kac]: https://keepachangelog.com/en/1.1.0/
 [semver]: https://semver.org/
 
+## 11.0.0
+
+### Read before upgrading
+
+**`register()` returns a result, not a user.** One line changes in your app,
+and the reason is a bug this fixes.
+
+Registration succeeding and authentication succeeding are different outcomes.
+A project with `require_verified_contact` enabled creates the account and
+issues **no session** — the user verifies their email before their first
+sign-in. The server has always answered that case correctly: 201 with
+`verification_required`, deliberately not an error, because reporting failure
+for a signup that worked is worse than either alternative.
+
+The SDK ignored that field. It built a session from a response body with no
+tokens in it, persisted it, and answered `currentUser` with a user whose every
+authenticated request went out as `Bearer undefined` and came back 401 —
+signed in as far as the app could tell, and unable to do anything. Silent, and
+only in the configuration that requires verification.
+
+```ts
+// Before
+const user = await Koolbase.auth.register({ email, password });
+
+// After
+const result = await Koolbase.auth.register({ email, password });
+switch (result.status) {
+  case 'authenticated':
+    // result.session is live, the user is signed in
+    break;
+  case 'verification_required':
+    // the account exists, result.session is null, they verify first
+    break;
+}
+```
+
+A discriminated union rather than a nullable session, so there is no path
+where an app reads `result.user` and assumes it is signed in. That is how the
+bug worked, and a nullable field would have allowed it at one remove.
+
+### Fixed
+
+- **A session is never fabricated from a response without tokens.** Every
+  path that builds one — register, login, refresh, Google, Apple — now refuses
+  a body claiming authentication while omitting a token, throwing
+  `MalformedSessionResponseError`. Distinct from `verification_required`,
+  which is a legitimate session-less success: this is a protocol violation and
+  says so.
+
+- **A pending signup no longer touches existing state.** It persists nothing,
+  fires no auth-state change, and leaves a session already on the device
+  alone — registering a second account does not sign out the first.
+
+### Migration
+
+Assign the result, switch on `status`. If your project does not require
+verified contact, the `authenticated` branch is the only one you will see —
+but write both, because turning that setting on later should not break your
+signup flow.
+
+## 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

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, () => _auth?.currentUser?.id ?? null);
-            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, () => _auth?.currentUser?.id ?? null);
-            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.3.0",
+  "version": "11.0.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.3.0"
+    "@koolbase/core": "11.0.0"
   },
   "publishConfig": {
     "access": "public"