fix: set default next pages export to client version, matching the default export (#3549)

* default pages export should be the client version

* added a changeset

Author: brandonhines-mialabs

.changeset/posthog-next-pages-default-client.md

@@ -0,0 +1,5 @@
+---
+'@posthog/next': patch
+---
+
+Fix `@posthog/next/pages` default export condition to resolve to the client barrel (`pages.client.js`) instead of the server barrel (`pages.js`), matching the behavior of the root `"."` export. This prevents bundlers that don't match a more specific condition from pulling in `server-only` and `posthog-node` unnecessarily.

packages/next/package.json

@@ -38,7 +38,7 @@
             "worker": "./dist/pages.edge.js",
             "browser": "./dist/pages.client.js",
             "react-server": "./dist/pages.js",
-            "default": "./dist/pages.js"
+            "default": "./dist/pages.client.js"
         }
     },
     "main": "./dist/index.client.js",

packages/next/tests/packaging.test.ts

@@ -50,7 +50,7 @@ describe('package.json#exports routing', () => {
         expect(pages.edge).toBe('./dist/pages.edge.js')
         expect(pages.worker).toBe('./dist/pages.edge.js')
         expect(pages['react-server']).toBe('./dist/pages.js')
-        expect(pages.default).toBe('./dist/pages.js')
+        expect(pages.default).toBe('./dist/pages.client.js')
     })
 
     it('. (root entry) keeps the existing per-runtime split intact', () => {