cloudflare-next-intl 0.6.28 → 0.6.29

package/dist/src/error_handling/create_server_error_action.d.ts

@@ -26,6 +26,12 @@ import { type ReportErrorConfig } from './report_error';
  * boundary (Next.js server actions serialize arguments; an `Error` instance
  * doesn't survive that intact) and `isClient: true` is set automatically.
  *
+ * Also attaches `requestContext: { path, userAgent, referer }` (best-effort,
+ * via `next/headers` — see `resolveRequestContext`) alongside your own
+ * `params`, so `onError`/the console report shows WHERE the error happened,
+ * not just what it was — useful when diagnosing a client error without a
+ * repro, since the page and browser are often the missing piece.
+ *
  * @param config Pass the relevant slices of your `RoutingConfig` directly —
  *   `{ errorHandling: config.errorHandling, generate: config.generate }`.
  */

package/dist/src/error_handling/create_server_error_action.js

@@ -1,5 +1,26 @@
 import reportError from './report_error';
 import stringifyUnknown from './stringify_unknown';
+/**
+ * Reads request context (page path, user agent, referer) via `next/headers`
+ * for a client-originated error report. `path` comes from `x-pathname`, set
+ * by `intlMiddleware` (this package's own middleware) — falls back to
+ * `undefined` when a header is missing (e.g. middleware didn't run for this
+ * request) rather than throwing.
+ */
+async function resolveRequestContext() {
+    try {
+        const { headers } = await import('next/headers');
+        const headerList = await headers();
+        return {
+            path: headerList.get('x-pathname') ?? undefined,
+            userAgent: headerList.get('user-agent') ?? undefined,
+            referer: headerList.get('referer') ?? undefined,
+        };
+    }
+    catch {
+        return {};
+    }
+}
 /**
  * Builds a function that reports a client-originated error via
  * `reportError`, meant to be re-exported directly from your OWN
@@ -26,15 +47,28 @@ import stringifyUnknown from './stringify_unknown';
  * boundary (Next.js server actions serialize arguments; an `Error` instance
  * doesn't survive that intact) and `isClient: true` is set automatically.
  *
+ * Also attaches `requestContext: { path, userAgent, referer }` (best-effort,
+ * via `next/headers` — see `resolveRequestContext`) alongside your own
+ * `params`, so `onError`/the console report shows WHERE the error happened,
+ * not just what it was — useful when diagnosing a client error without a
+ * repro, since the page and browser are often the missing piece.
+ *
  * @param config Pass the relevant slices of your `RoutingConfig` directly —
  *   `{ errorHandling: config.errorHandling, generate: config.generate }`.
  */
 export default function createServerErrorAction(config) {
     return async function reportClientError(error, classOrMethodName, params) {
+        const requestContext = await resolveRequestContext();
+        const isPlainParamsObject = typeof params === 'object' && params !== null && !Array.isArray(params);
+        const mergedParams = params === undefined
+            ? { requestContext }
+            : isPlainParamsObject
+                ? { ...params, requestContext }
+                : { params, requestContext };
         await reportError(config, {
             error: stringifyUnknown(error, true),
             classOrMethodName,
-            params,
+            params: mergedParams,
             isClient: true,
         });
     };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "cloudflare-next-intl",
-  "version": "0.6.28",
+  "version": "0.6.29",
   "description": "Optimized Next Intl Package Special for App Router and Cloudflare",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",