@coreiam/auth 1.0.7 → 1.0.8

package/dist/nextjs/provider.js

@@ -16,9 +16,9 @@ const AuthContext = (0, react_1.createContext)({
     register: async () => ({ error: 'CoreIAMProvider is not mounted' }),
     refetchIdentity: async () => { },
 });
-function CoreIAMProvider({ children, initialIdentity = null, redirects = {}, }) {
-    const [identity, setIdentity] = (0, react_1.useState)(initialIdentity);
-    const [isLoading, setIsLoading] = (0, react_1.useState)(initialIdentity === null);
+function CoreIAMProvider({ children, initialIdentity, redirects = {}, }) {
+    const [identity, setIdentity] = (0, react_1.useState)(initialIdentity ?? null);
+    const [isLoading, setIsLoading] = (0, react_1.useState)(initialIdentity === undefined);
     const router = (0, navigation_1.useRouter)();
     const refetchIdentity = async () => {
         try {
@@ -33,7 +33,16 @@ function CoreIAMProvider({ children, initialIdentity = null, redirects = {}, })
         }
     };
     (0, react_1.useEffect)(() => {
-        if (initialIdentity === null) {
+        // FIX: was `initialIdentity === null`, which can't tell "SSR ran and
+        // confirmed you're logged out" (a correct, final null) apart from "no
+        // SSR value was ever provided" (a real undefined). Since layout.tsx
+        // always calls getSession() and passes its result — even when that
+        // result legitimately is null — every logged-out page view was
+        // treated as "no SSR value, fetch again," firing a second, wholly
+        // redundant /auth/profile call for something SSR had already
+        // determined. undefined (the prop genuinely omitted) is the only case
+        // that should trigger this fallback fetch.
+        if (initialIdentity === undefined) {
             refetchIdentity();
         }
         else {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@coreiam/auth",
-  "version": "1.0.7",
+  "version": "1.0.8",
   "main": "./dist/core/index.js",
   "types": "./dist/core/index.d.ts",
   "exports": {