cloudflare-next-intl 0.6.3 → 0.6.4

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

@@ -1,13 +1,26 @@
 import type { ErrorHandlingParams } from '../types/types';
 import { type ReportErrorConfig } from './report_error';
 /**
- * Creates a `"use server"` action that reports a client-originated error via
- * `reportError`, so `config` (and anything it closes over — secrets,
+ * Builds a function that reports a client-originated error via
+ * `reportError`, meant to be re-exported directly from your OWN
+ * `"use server"` file so `config` (and anything it closes over — secrets,
  * `Secrets.telegramBotToken`-style env reads inside your `onError`) never
- * has to be imported into client-side code. Call this once (server-side,
- * e.g. next to your `RoutingConfig`) and pass the returned function to
- * client components that need to report an error — they only ever handle
- * the error value itself, never `config`.
+ * has to be imported into client-side code:
+ *
+ * ```ts
+ * // report_client_error.ts
+ * "use server";
+ * import createServerErrorAction from "cloudflare-next-intl/createServerErrorAction";
+ * import intlConfig from "./intl_config";
+ * export const reportClientError = createServerErrorAction(intlConfig);
+ * ```
+ *
+ * This function itself must NOT be called from a file marked `"use server"`
+ * — Next.js requires every top-level export of such a file to be an async
+ * function directly; a factory that returns one doesn't qualify. Put
+ * `"use server"` in your OWN file (as above), not in a file that calls
+ * `createServerErrorAction` and re-exports its result under a different
+ * name than a plain `const`.
  *
  * The error is stringified before crossing the client→server action
  * boundary (Next.js server actions serialize arguments; an `Error` instance

package/dist/src/error_handling/create_server_error_action.js

@@ -1,14 +1,26 @@
-"use server";
 import reportError from './report_error';
 import stringifyUnknown from './stringify_unknown';
 /**
- * Creates a `"use server"` action that reports a client-originated error via
- * `reportError`, so `config` (and anything it closes over — secrets,
+ * Builds a function that reports a client-originated error via
+ * `reportError`, meant to be re-exported directly from your OWN
+ * `"use server"` file so `config` (and anything it closes over — secrets,
  * `Secrets.telegramBotToken`-style env reads inside your `onError`) never
- * has to be imported into client-side code. Call this once (server-side,
- * e.g. next to your `RoutingConfig`) and pass the returned function to
- * client components that need to report an error — they only ever handle
- * the error value itself, never `config`.
+ * has to be imported into client-side code:
+ *
+ * ```ts
+ * // report_client_error.ts
+ * "use server";
+ * import createServerErrorAction from "cloudflare-next-intl/createServerErrorAction";
+ * import intlConfig from "./intl_config";
+ * export const reportClientError = createServerErrorAction(intlConfig);
+ * ```
+ *
+ * This function itself must NOT be called from a file marked `"use server"`
+ * — Next.js requires every top-level export of such a file to be an async
+ * function directly; a factory that returns one doesn't qualify. Put
+ * `"use server"` in your OWN file (as above), not in a file that calls
+ * `createServerErrorAction` and re-exports its result under a different
+ * name than a plain `const`.
  *
  * The error is stringified before crossing the client→server action
  * boundary (Next.js server actions serialize arguments; an `Error` instance

package/package.json

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