cloudflare-next-intl 0.4.5 → 0.5.0

package/dist/src/cookie_consent/client/components/clarity_script.d.ts

@@ -1,13 +1,9 @@
 /**
  * Loads and initializes Microsoft Clarity. Split into its own module and
- * loaded via `next/dynamic` from `cookie_consent_analytics.tsx` — bundlers
- * (webpack/Turbopack) resolve every literal `import()` specifier they can
- * reach at build time, so keeping this file's `import('@microsoft/clarity')`
- * out of the main analytics module means consumers who never set
- * `secrets.clarityProjectId` (and never render this component) don't need
- * `@microsoft/clarity` (an optional peer dependency) installed at all — the
- * dynamic-imported chunk containing this file is only built/requested the
- * first time it's actually rendered.
+ * loaded via `next/dynamic` from `cookie_consent_analytics.tsx` so it's
+ * only fetched as a separate chunk once actually rendered (consent granted
+ * and `secrets.clarityProjectId` set) — `@microsoft/clarity` is a real
+ * dependency of this package, so it's always installed regardless.
  */
 export default function ClarityScript({ projectId }: {
     projectId: string;

package/dist/src/cookie_consent/client/components/clarity_script.js

@@ -9,14 +9,10 @@ function getClarityModule() {
 }
 /**
  * Loads and initializes Microsoft Clarity. Split into its own module and
- * loaded via `next/dynamic` from `cookie_consent_analytics.tsx` — bundlers
- * (webpack/Turbopack) resolve every literal `import()` specifier they can
- * reach at build time, so keeping this file's `import('@microsoft/clarity')`
- * out of the main analytics module means consumers who never set
- * `secrets.clarityProjectId` (and never render this component) don't need
- * `@microsoft/clarity` (an optional peer dependency) installed at all — the
- * dynamic-imported chunk containing this file is only built/requested the
- * first time it's actually rendered.
+ * loaded via `next/dynamic` from `cookie_consent_analytics.tsx` so it's
+ * only fetched as a separate chunk once actually rendered (consent granted
+ * and `secrets.clarityProjectId` set) — `@microsoft/clarity` is a real
+ * dependency of this package, so it's always installed regardless.
  */
 export default function ClarityScript({ projectId }) {
     useEffect(() => {

package/dist/src/cookie_consent/client/components/cookie_consent_analytics.js

@@ -3,12 +3,10 @@ import { jsx as _jsx, Fragment as _Fragment, jsxs as _jsxs } from "react/jsx-run
 import { useEffect } from 'react';
 import dynamic from 'next/dynamic';
 import useCookieConsent from '../use_cookie_consent';
-// Hoisted to module scope, like this package's other `dynamic()` calls —
-// calling it inside the component body would create a new component
-// identity every render. Deferring to a separate chunk keeps
-// `@microsoft/clarity`'s `import()` (in `clarity_script.tsx`) out of this
-// module, so bundlers only resolve it when `ClarityScript` is actually
-// rendered — see that file's doc comment for why this matters.
+// Hoisted to module scope — calling `dynamic()` inside the component body
+// creates a brand-new component identity every render, forcing a
+// remount. Splitting into a separate chunk keeps `@microsoft/clarity`'s
+// import out of this module until `ClarityScript` is actually rendered.
 const ClarityScript = dynamic(() => import('./clarity_script'));
 /**
  * Renders whichever analytics/ads scripts have a resolved secret, gated on

package/dist/src/cookie_consent/gdpr_countries.d.ts

@@ -8,8 +8,8 @@ export declare const defaultGdprCountries: readonly string[];
 /**
  * Resolves whether the cookie-consent banner is required for a visitor.
  *
- * - Neither getter set: country-based gating is off entirely — consent is
- *   never required (the simplest opt-in-by-default setup).
+ * - Neither getter set: fail-safe — consent is required by default since
+ *   the visitor's country can't be determined at all.
  * - Either getter set: fail-safe — a country that couldn't be resolved
  *   still requires consent; only a resolved country OUTSIDE
  *   `gdprCountries` skips the banner. `getCountryCode` takes precedence

package/dist/src/cookie_consent/gdpr_countries.js

@@ -33,8 +33,8 @@ function getGdprCountriesSet(gdprCountries) {
 /**
  * Resolves whether the cookie-consent banner is required for a visitor.
  *
- * - Neither getter set: country-based gating is off entirely — consent is
- *   never required (the simplest opt-in-by-default setup).
+ * - Neither getter set: fail-safe — consent is required by default since
+ *   the visitor's country can't be determined at all.
  * - Either getter set: fail-safe — a country that couldn't be resolved
  *   still requires consent; only a resolved country OUTSIDE
  *   `gdprCountries` skips the banner. `getCountryCode` takes precedence
@@ -42,7 +42,7 @@ function getGdprCountriesSet(gdprCountries) {
  */
 export default async function resolveRequiresConsent(getCountryCode, getCloudflareContext, gdprCountries) {
     if (!getCountryCode && !getCloudflareContext)
-        return false;
+        return true;
     const countryCode = getCountryCode
         ? await getCountryCode()
         : (await getCloudflareContext({ async: true }))?.cf?.country;

package/dist/src/server/components/server_provider.js

@@ -59,8 +59,17 @@ export default async function LocationzationProvider({ language, messages, child
     let analyticsSecrets;
     let requiresConsent = true;
     if (config.cookieConsent) {
-        requiresConsent = await resolveRequiresConsent(config.cookieConsent.getCountryCode, config.cookieConsent.getCloudflareContext, config.cookieConsent.gdprCountries);
         const isDevEnvironment = process.env.NODE_ENV === 'development';
+        // `getCloudflareContext` under `next dev`'s Cloudflare dev shim can
+        // crash the local workerd process (a native RPC panic, not a
+        // catchable JS error — see cloudflare/workers-sdk#8687) merely by
+        // being called, regardless of what it resolves to. `getCountryCode`
+        // is caller-supplied and may be dev-safe, so only skip the
+        // `getCloudflareContext` path in dev; fail-safe to `true`
+        // (banner shown) same as an unresolved country would.
+        requiresConsent = !isDevEnvironment
+            ? await resolveRequiresConsent(config.cookieConsent.getCountryCode, config.cookieConsent.getCloudflareContext, config.cookieConsent.gdprCountries)
+            : true;
         const analyticsAllowedInEnv = config.cookieConsent.enableAnalyticsInDevMode === true || !isDevEnvironment;
         if (config.cookieConsent.autoWireAnalytics !== false && analyticsAllowedInEnv) {
             analyticsSecrets = config.cookieConsent.getSecrets

package/dist/src/types/types.d.ts

@@ -155,10 +155,9 @@ export interface CookieConsentRoutingConfig {
      * `getCloudflareContext`) decides whether the cookie-consent banner is
      * required at all: visitors outside `gdprCountries` skip the banner and
      * get analytics immediately (still gated by `enableAnalyticsInDevMode`).
-     * Omit BOTH to skip country-based gating entirely — the banner is never
-     * shown and consent is treated as implicitly granted for everyone. This
-     * is the simplest opt-in-by-default setup; set one of the two getters
-     * once you need real GDPR-region gating.
+     * Omit BOTH to require consent for everyone (fail-safe default — the
+     * visitor's country can't be determined at all without either getter).
+     * Set one of the two getters to scope the banner to GDPR regions only.
      */
     getCloudflareContext?: CookieConsentGetCloudflareContext;
     /**
@@ -219,7 +218,11 @@ export interface CookieConsentAnalyticsSecrets {
     googleAdsId?: string;
     /** Google AdSense publisher ID, e.g. `"ca-pub-XXXXXXXXXXXXXXXX"`. */
     googleAdSenseId?: string;
-    /** Microsoft Clarity project ID. */
+    /**
+     * Microsoft Clarity project ID. `@microsoft/clarity` is a real
+     * dependency of this package (small, so always installed) — loaded and
+     * initialized automatically once consent is granted.
+     */
     clarityProjectId?: string;
 }
 export interface FirebaseAuthRoutingConfig {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "cloudflare-next-intl",
-  "version": "0.4.5",
+  "version": "0.5.0",
   "description": "Optimized Next Intl Package Special for App Router and Cloudflare",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",
@@ -181,8 +181,10 @@
     "url": "https://github.com/demian-ilnytskyi/cloudflare-next-intl/issues"
   },
   "homepage": "https://github.com/demian-ilnytskyi/cloudflare-next-intl#readme",
+  "dependencies": {
+    "@microsoft/clarity": "^1.0.2"
+  },
   "peerDependencies": {
-    "@microsoft/clarity": ">=1.0.0",
     "firebase": ">=10.0.0",
     "next": ">=12.0.0",
     "react": "^16.8.0 || ^17.0.0 || ^18.0.0 || >=19.0.0-rc <19.0.0 || ^19.0.0",
@@ -194,15 +196,11 @@
     },
     "firebase": {
       "optional": true
-    },
-    "@microsoft/clarity": {
-      "optional": true
     }
   },
   "devDependencies": {
     "@eslint/eslintrc": "^3",
     "@eslint/js": "^9.27.0",
-    "@microsoft/clarity": "^1.0.2",
     "@testing-library/dom": "^10.4.1",
     "@testing-library/jest-dom": "^7.0.0",
     "@testing-library/react": "^16.3.2",