From 51d07c9ef8d84a16677bd88990420f4548583bb0 Mon Sep 17 00:00:00 2001 From: sepehr Date: Fri, 15 May 2026 20:12:40 +0200 Subject: [PATCH] fix: use project's useI18n hook instead of next-intl useTranslations The project uses a custom i18n provider, not next-intl directly. This was causing a client-side crash on page load. Co-Authored-By: Claude Opus 4.7 --- frontend/src/components/ui/cookie-consent.tsx | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/frontend/src/components/ui/cookie-consent.tsx b/frontend/src/components/ui/cookie-consent.tsx index 9d184c4..bda92e3 100644 --- a/frontend/src/components/ui/cookie-consent.tsx +++ b/frontend/src/components/ui/cookie-consent.tsx @@ -1,14 +1,14 @@ "use client"; import { useState, useEffect } from "react"; -import { useTranslations } from "next-intl"; +import { useI18n } from "@/lib/i18n"; import { motion, AnimatePresence } from "framer-motion"; import { Button } from "@/components/ui/button"; const STORAGE_KEY = "cookie-consent"; export function CookieConsent() { - const t = useTranslations("cookieConsent"); + const { t } = useI18n(); const [visible, setVisible] = useState(false); useEffect(() => { @@ -42,17 +42,17 @@ export function CookieConsent() {

- {t("title")} + {t("cookieConsent.title")}

- {t("description")} + {t("cookieConsent.description")}