posthog-node 5.1.0 → 5.1.1

package/CHANGELOG.md

@@ -1,5 +1,9 @@
 # Next
 
+# 5.1.1 - 2025-06-16
+
+1. fix: Handle double-encoded JSON payloads from the remote config endpoint
+
 # 5.1.0 - 2025-06-12
 
 1. chore: use `/flags?v=2&config=true` instead of `/decide?v=4` for the flag evaluation backend

package/lib/edge/index.cjs

@@ -935,7 +935,7 @@ function setupExpressErrorHandler(_posthog, app) {
   });
 }
 
-var version = "5.1.0";
+var version = "5.1.1";
 
 var PostHogPersistedProperty;
 (function (PostHogPersistedProperty) {
@@ -3164,7 +3164,24 @@ class PostHogBackendClient extends PostHogCoreStateless {
     return response;
   }
   async getRemoteConfigPayload(flagKey) {
-    return (await this.featureFlagsPoller?._requestRemoteConfigPayload(flagKey))?.json();
+    const response = await this.featureFlagsPoller?._requestRemoteConfigPayload(flagKey);
+    if (!response) {
+      return undefined;
+    }
+    const parsed = await response.json();
+    // The payload from the endpoint is stored as a JSON encoded string. So when we return
+    // it, it's effectively double encoded. As far as we know, we should never get single-encoded
+    // JSON, but we'll be defensive here just in case.
+    if (typeof parsed === 'string') {
+      try {
+        // If the parsed value is a string, try parsing it again to handle double-encoded JSON
+        return JSON.parse(parsed);
+      } catch (e) {
+        // If second parse fails, return the string as is
+        return parsed;
+      }
+    }
+    return parsed;
   }
   async isFeatureEnabled(key, distinctId, options) {
     const feat = await this.getFeatureFlag(key, distinctId, options);