cloudflare-next-intl 0.9.37 → 0.9.38

package/README.md

@@ -627,6 +627,34 @@ server-side resolution) on `ErrorHandlingParams` — reporting is skipped
 whenever `consent` is set and not `true`, since sending error reports to a
 third party without consent can itself be GDPR-relevant.
 
+#### Reporting client-side errors
+
+`reportClientError` is a ready-made server action for a client component's
+own `catch`/error boundary — it resolves your `errorHandling`/`generate`
+config through `@intl-config` (the alias `db`/`clearSessionAction` already
+use — see "Setup" above), so there's no wrapper file or setup call beyond
+that alias:
+
+```typescript
+// some_client_component.tsx
+"use client";
+import reportClientError from "cloudflare-next-intl/reportClientError";
+
+try {
+    await riskyClientThing();
+} catch (error) {
+    void reportClientError(error, "riskyClientThing");
+}
+```
+
+The error is stringified before it crosses the action boundary — no need to
+normalize it into an `Error` yourself first, even a non-`Error` throw or an
+unresolved React reference stub comes through safely — and `isClient: true`
+plus a best-effort `requestContext: { path, userAgent, referer }` (via
+`next/headers`) are attached automatically. Prefer `createServerErrorAction`
+instead if you want config bound explicitly per call rather than resolved
+through `@intl-config`.
+
 #### Stale Deploy & Chunk Load Error Recovery
 
 When a new version of your application is deployed to Cloudflare Workers, users on older client sessions may encounter `ChunkLoadError` or failed dynamic imports when requesting outdated chunks.

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

@@ -10,5 +10,4 @@ export { defaultIgnoredConsoleErrors } from './default_ignored_console_errors.js
 export { default as isStaleDeployError, defaultStaleDeployPatterns, setStaleDeployPatterns, getStaleDeployPatterns, } from './is_stale_deploy_error.js';
 export { default as clearClientCache } from './clear_client_cache.js';
 export { default as useStaleDeployRecovery, shouldRecoverFromStaleDeploy } from './use_stale_deploy_recovery.js';
-export { setErrorHandlingActionConfig, getErrorHandlingActionConfig } from './error_handling_action_config.js';
 export type { ErrorHandlingParams, ErrorHandlingRoutingConfig } from '../types/types.js';

package/dist/src/error_handling/index.js

@@ -8,4 +8,3 @@ export { defaultIgnoredConsoleErrors } from './default_ignored_console_errors.js
 export { default as isStaleDeployError, defaultStaleDeployPatterns, setStaleDeployPatterns, getStaleDeployPatterns, } from './is_stale_deploy_error.js';
 export { default as clearClientCache } from './clear_client_cache.js';
 export { default as useStaleDeployRecovery, shouldRecoverFromStaleDeploy } from './use_stale_deploy_recovery.js';
-export { setErrorHandlingActionConfig, getErrorHandlingActionConfig } from './error_handling_action_config.js';

package/dist/src/error_handling/report_client_error_action.js

@@ -1,6 +1,6 @@
 'use server';
-import { getErrorHandlingActionConfig } from './error_handling_action_config.js';
+import config from '@intl-config';
 import { reportClientErrorCore } from './report_client_error_core.js';
 export default async function reportClientError(error, classOrMethodName, params) {
-    await reportClientErrorCore(getErrorHandlingActionConfig(), error, classOrMethodName, params);
+    await reportClientErrorCore(config, error, classOrMethodName, params);
 }

package/llms.txt

@@ -34,6 +34,7 @@ other subpath can be used.
 - `./clearClientCache` — `clearClientCache()`: async helper wiping `window.caches`, unregistering service workers, and clearing `sessionStorage` for recovering from stale deployments.
 - `useStaleDeployRecovery(error, onRecover?, delayMs?)` (client hook, in `./errorHandling`) — once per build id (`localStorage['buildId']`, `sessionStorage` marker), waits `delayMs` (default 5000ms), runs optional `onRecover()` + `clearClientCache()` in parallel, then `window.location.reload()`. Returns whether a reload is pending, so caller renders a loading state instead of error UI. Recovers even past the one-reload cap when `localStorage['buildIdSetAt']` is <60s old (new deploy still settling). `shouldRecoverFromStaleDeploy(error, buildId, marker, recentBuild?)` and `isRecentBuild(setAt, now, windowMs?)` are the pure predicates.
 - `./createServerErrorAction` — `createServerErrorAction(action, config)`: wrapper for server actions with standardized error reporting.
+- `./reportClientError` — `reportClientError(error, classOrMethodName, params?)`: ready-made `"use server"` action reporting a client-originated error, config resolved via `@intl-config` (no per-app wrapper file or setup call needed, unlike `createServerErrorAction`).
 
 ## `firebaseAuth*` subpaths (require `firebaseAuth` set on your `RoutingConfig`)
 

package/package.json

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

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

@@ -1,3 +0,0 @@
-import type { ReportErrorConfig } from './report_error.js';
-export declare function setErrorHandlingActionConfig(next: ReportErrorConfig | undefined): void;
-export declare function getErrorHandlingActionConfig(): ReportErrorConfig | undefined;

package/dist/src/error_handling/error_handling_action_config.js

@@ -1,7 +0,0 @@
-let config;
-export function setErrorHandlingActionConfig(next) {
-    config = next;
-}
-export function getErrorHandlingActionConfig() {
-    return config;
-}