@hexclave/sc 1.0.3 → 1.0.5

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hexclave/sc",
-  "version": "1.0.3",
+  "version": "1.0.5",
   "repository": "https://github.com/hexclave/hexclave",
   "exports": {
     "./force-react-server": {
@@ -36,6 +36,7 @@
   "files": [
     "README.md",
     "dist",
+    "src",
     "CHANGELOG.md",
     "LICENSE"
   ],

package/src/index.combined.ts

@@ -0,0 +1,6 @@
+import * as def from "./index.default";
+import * as reactServer from "./index.react-server";
+
+export declare const cookies: typeof reactServer.cookies | typeof def.cookies;
+export declare const headers: typeof reactServer.headers | typeof def.headers;
+export declare const isReactServer: boolean;

package/src/index.default.ts

@@ -0,0 +1,3 @@
+export const cookies = undefined;
+export const headers = undefined;
+export const isReactServer = false;

package/src/index.react-server.ts

@@ -0,0 +1,10 @@
+export const isReactServer = true;
+
+
+// In Next.js 15, the `next/headers` module returns async functions.
+// Since we support both Next.js 14 and 15, we return a union of the two.
+// TODO: Remove this once we drop support for Next.js 14, and replace it with `export { cookies, headers } from 'next/headers';`
+// https://nextjs.org/blog/next-15#async-request-apis-breaking-change
+import { cookies as nextCookies, headers as nextHeaders } from './next-static-analysis-workaround';
+export const cookies = nextCookies as typeof nextCookies | ((...args: Parameters<typeof nextCookies>) => Promise<ReturnType<typeof nextCookies>>);
+export const headers = nextHeaders as typeof nextHeaders | ((...args: Parameters<typeof nextHeaders>) => Promise<ReturnType<typeof nextHeaders>>);

package/src/next-static-analysis-workaround.ts

@@ -0,0 +1,11 @@
+// Next statically analyzes the imports and ensures that the `next/headers` module is never imported on a client bundle.
+//
+// We know what we're doing though. We ensure at runtime that we never use the module unless we're on the server, so the
+// static analysis is wrong.
+//
+// Fortunately, as a hack, we can get around it by importing them using the `export from` syntax, which the static
+// analyzer does not detect, but Webpack is fine with it.
+//
+// So, we can use the export syntax here, and then import them normally in the main file.
+
+export * from 'next/headers';