•apps/dashboard/messages/en.json
•apps/dashboard/messages/zh.json
•apps/dashboard/next.config.mjs
•apps/dashboard/package.json
•apps/dashboard/src/app/(main)/(protected)/(outside-dashboard)/new-project/page-client.tsx
•apps/dashboard/src/app/(main)/(protected)/(outside-dashboard)/projects/page-client.tsx
•apps/dashboard/src/app/(main)/(protected)/projects/[projectId]/(overview)/globe.tsx
•apps/dashboard/src/app/(main)/(protected)/projects/[projectId]/(overview)/line-chart.tsx
•apps/dashboard/src/app/(main)/(protected)/projects/[projectId]/(overview)/metrics-page.tsx
•apps/dashboard/src/app/(main)/(protected)/projects/[projectId]/(overview)/setup-page.tsx
•apps/dashboard/src/app/(main)/(protected)/projects/[projectId]/api-keys/page-client.tsx
•apps/dashboard/src/app/(main)/(protected)/projects/[projectId]/domains/page-client.tsx
•apps/dashboard/src/app/(main)/(protected)/projects/[projectId]/email-drafts/page-client.tsx
•apps/dashboard/src/app/(main)/(protected)/projects/[projectId]/email-templates/page-client.tsx
•apps/dashboard/src/app/(main)/(protected)/projects/[projectId]/email-themes/page-client.tsx
•apps/dashboard/src/app/(main)/(protected)/projects/[projectId]/emails/page-client.tsx
•apps/dashboard/src/app/(main)/(protected)/projects/[projectId]/payments/transactions/page-client.tsx
•apps/dashboard/src/app/(main)/(protected)/projects/[projectId]/project-permissions/page-client.tsx
•apps/dashboard/src/app/(main)/(protected)/projects/[projectId]/project-settings/page-client.tsx
•apps/dashboard/src/app/(main)/(protected)/projects/[projectId]/sidebar-layout.tsx
•apps/dashboard/src/app/(main)/(protected)/projects/[projectId]/team-permissions/page-client.tsx
•apps/dashboard/src/app/(main)/(protected)/projects/[projectId]/team-settings/page-client.tsx
•apps/dashboard/src/app/(main)/(protected)/projects/[projectId]/teams/page-client.tsx
•apps/dashboard/src/app/(main)/(protected)/projects/[projectId]/users/[userId]/page-client.tsx
•apps/dashboard/src/app/(main)/(protected)/projects/[projectId]/users/page-client.tsx
•apps/dashboard/src/app/(main)/(protected)/projects/[projectId]/webhooks/page-client.tsx
•apps/dashboard/src/app/(main)/i18n-test/page.tsx
•apps/dashboard/src/app/layout.tsx
•apps/dashboard/src/components/data-table/api-key-table.tsx
•apps/dashboard/src/components/data-table/payment-item-table.tsx
•apps/dashboard/src/components/data-table/payment-product-table.tsx
•apps/dashboard/src/components/data-table/permission-table.tsx
•apps/dashboard/src/components/data-table/team-member-table.tsx
•apps/dashboard/src/components/data-table/team-table.tsx
•apps/dashboard/src/components/data-table/transaction-table.tsx
•apps/dashboard/src/components/data-table/user-table.tsx
•apps/dashboard/src/components/language-switcher.tsx
•apps/dashboard/src/components/navbar.tsx
•apps/dashboard/src/components/user-dialog.tsx
•apps/dashboard/src/i18n/request.ts
•apps/dashboard/src/i18n/routing.ts
•docker/dependencies/README.md
•docker/dependencies/docker.compose.minimal.yaml
•package.json
•packages/stack-ui/src/components/data-table/data-table.tsx
•packages/stack-ui/src/components/data-table/pagination.tsx
•packages/stack-ui/src/components/data-table/toolbar.tsx
•packages/stack-ui/src/components/data-table/view-options.tsx
•pnpm-lock.yaml
•scripts/check-docker.sh

diff --git a/apps/dashboard/src/middleware.tsx b/apps/dashboard/src/middleware.tsxindex 8e71b71e..384b974d 100644--- a/apps/dashboard/src/middleware.tsx+++ b/apps/dashboard/src/middleware.tsx@@ -5,6 +5,8 @@ import { StackAssertionError } from '@stackframe/stack-shared/dist/utils/errors' import { wait } from '@stackframe/stack-shared/dist/utils/promises'; import type { NextRequest } from 'next/server'; import { NextResponse } from 'next/server';+import createIntlMiddleware from 'next-intl/middleware';+import { routing } from './i18n/routing';  const corsAllowedRequestHeaders = [   // General@@ -34,6 +36,8 @@ const corsAllowedResponseHeaders = [   'x-stack-known-error', ];+const intlMiddleware = createIntlMiddleware(routing);+ export async function middleware(request: NextRequest) {   const delay = Number.parseInt(getEnvVariable('STACK_ARTIFICIAL_DEVELOPMENT_DELAY_MS', '0'));   if (delay) {@@ -48,28 +52,32 @@ export async function middleware(request: NextRequest) {   const url = new URL(request.url);   const isApiRequest = url.pathname.startsWith('/api/');-  // default headers-  const responseInit: ResponseInit = {-    headers: {-      // CORS headers-      ...!isApiRequest ? {} : {+  // Skip i18n middleware for API routes+  if (isApiRequest) {+    // default headers for API routes+    const responseInit: ResponseInit = {+      headers: {+        // CORS headers         "Access-Control-Allow-Origin": "*",         "Access-Control-Allow-Methods": "GET, POST, PUT, DELETE, OPTIONS",         "Access-Control-Allow-Headers": corsAllowedRequestHeaders.join(', '),         "Access-Control-Expose-Headers": corsAllowedResponseHeaders.join(', '),       },-    },-  };+    };++    // we want to allow preflight requests to pass through+    // even if the API route does not implement OPTIONS+    if (request.method === 'OPTIONS') {+      return new Response(null, responseInit);+    }-  // we want to allow preflight requests to pass through-  // even if the API route does not implement OPTIONS-  if (request.method === 'OPTIONS' && isApiRequest) {-    return new Response(null, responseInit);+    return NextResponse.next(responseInit);   }-  return NextResponse.next(responseInit);+  // Handle i18n for non-API routes+  return intlMiddleware(request); }  export const config = {-  matcher: '/:path*',+  matcher: ['/((?!api|_next|_vercel|.*\\..*).*)', '/api/v1/auth/signin'], };

Analysis

Missing next-intl middleware integration prevents locale detection

What fails: The middleware inapps/dashboard/src/middleware.tsx lacks next-intl integration, causingrequestLocale ingetRequestConfig() to always be undefined, forcing the system to rely solely on cookies for locale detection.

How to reproduce:

1. Visit dashboard without existing locale cookie
2. Check network requests - nox-next-intl-locale header is attached
3. Server-side rendering defaults to fallback locale instead of browser preference

Result: The locale detection priority order (request → cookie → default) is broken. Browser language preferences are ignored on initial page load.

Expected: Pernext-intl middleware docs, middleware should handle locale negotiation and attach locale headers even whenlocalePrefix: 'never' is configured.

apps/dashboard/src/app/(main)/(protected)/(outside-dashboard)/new-project/page-client.tsx (1)

29-36:Memoize the schema to avoid recreation on every render.

TheprojectFormSchema is recreated on every component render, which is inefficient. Since the schema depends on the translation functiont, wrap it inuseMemo witht as a dependency.

Apply this diff:

+import { useMemo } from "react"; export default function PageClient() {   const t = useTranslations('newProject');   const user = useUser({ or: 'redirect', projectIdMustMatch: "internal" });   const [loading, setLoading] = useState(false);   const router = useRouter();   const searchParams = useSearchParams();   const displayName = searchParams.get("display_name");-  const projectFormSchema = yup.object({-    displayName: yup.string().min(1, t('validation.displayNameRequired')).defined().nonEmpty(t('validation.displayNameRequired')),-    signInMethods: yup.array(yup.string().oneOf(["credential", "magicLink", "passkey"].concat(allProviders)).defined())-      .min(1, t('validation.signInMethodRequired'))-      .defined(t('validation.signInMethodRequired')),-    teamId: yup.string().uuid().defined(t('validation.teamRequired')),-  });+  const projectFormSchema = useMemo(() => yup.object({+    displayName: yup.string().min(1, t('validation.displayNameRequired')).defined().nonEmpty(t('validation.displayNameRequired')),+    signInMethods: yup.array(yup.string().oneOf(["credential", "magicLink", "passkey"].concat(allProviders)).defined())+      .min(1, t('validation.signInMethodRequired'))+      .defined(t('validation.signInMethodRequired')),+    teamId: yup.string().uuid().defined(t('validation.teamRequired')),+  }), [t]);

apps/dashboard/src/components/user-dialog.tsx (1)

67-73:Consider using tErrors namespace for validation messages.

Line 69 usestHints('emailVerifiedRequired') for a Yup validation error message, while the same key is reused as a UI hint on line 151. Validation error messages typically belong in the error namespace for consistency and clarity. Consider either:

• UsingtErrors('emailVerifiedRequired') here and keepingtHints('emailVerifiedRequired') for the UI hint (separate keys with the same text in translation files), or
• Moving this totErrors and referencing that namespace on line 151 if the same message is appropriate in both contexts.

apps/dashboard/src/app/(main)/(protected)/projects/[projectId]/project-settings/page-client.tsx (2)

254-257:Avoid shadowing the translation functiont.

The callback parameter inteams.find(t => ...) on line 256 shadows the translation functiont. While this works due to scoping, it reduces code clarity.

Apply this diff to use a clearer parameter name:

 {t('transfer.confirm', {   projectName: project.displayName,-  teamName: teams.find(t => t.id === selectedTeamId)?.displayName+  teamName: teams.find(team => team.id === selectedTeamId)?.displayName })}

---

304-304:Consider consolidating sentence fragments for better translation flexibility.

Splitting a sentence across multiple translation keys (line 304) can cause issues in languages with different word orders. The bold text might need to appear in a different position in some languages.

Consider using a single translation key with ICU rich text formatting (next-intl supports this in v4+):

// In your translation file:{"dangerZone":{"irreversibleWarning":"This action is <bold>irreversible</bold>. This will permanently delete:"}}// In the component:{t.rich('dangerZone.irreversibleWarning',{bold:(chunks)=><strong>{chunks}</strong>})}

Alternatively, if keeping the current approach, ensure translators understand the context and sentence structure in all languages.

apps/dashboard/src/app/(main)/(protected)/projects/[projectId]/users/page-client.tsx (1)

29-29:Consider using a single translation key with rich text formatting.

The welcome message currently uses multiple separate translation calls concatenated together. This approach can make translation difficult as translators may not have full context.

Consider refactoring to use a single translation key with ICU message format for rich text:

{t.rich('welcomeMessage',{link:(chunks)=><StyledLinkhref="https://docs.stack-auth.com">{chunks}</StyledLink>})}

And update the translation file to:

{"welcomeMessage":"Welcome to Stack Auth! Check out our <link>documentation</link> to get started."}

This approach provides translators with full context and allows them to reorder elements as needed for different languages.

docker/dependencies/docker.compose.minimal.yaml (1)

108-108:Minor formatting: Remove extra blank line.

YAMLlint reports too many blank lines at the end of the file.

 volumes:   postgres-data:   inbucket-data:   svix-redis-data:   svix-postgres-data:   s3mock-data:   deno-cache:-

apps/dashboard/messages/zh.json (1)

1-1053:LGTM! Translation file structure is well-organized.

The Chinese translation file is comprehensive and properly structured to match the dashboard's i18n namespace hierarchy. A spot check reveals consistent placeholder formatting (e.g.,{userName},{teamName},{page}) and no obvious HTML injection risks.

However, consider these optional improvements:

1. Translation quality verification: Have a native Chinese speaker review technical terminology and UI strings for naturalness and accuracy.
2. Placeholder validation: Consider adding a build-time check to ensure all placeholders in translations match those in the English source (en.json).

apps/dashboard/src/components/language-switcher.tsx (2)

27-27:Consider smoother locale transition without full page refresh.

Callingrouter.refresh() triggers a full page reload, which may cause a jarring user experience. Next-intl and Next.js App Router support smoother locale transitions.

Consider using Next.js'suseRouter fromnext/navigation with a locale-aware approach, or investigate if next-intl provides a smoother transition mechanism that updates locale context without a hard refresh. The current implementation works but could be improved for better UX.

If a refresh is necessary due to server-side locale detection, document this decision in a comment explaining why a full refresh is required.

---

13-16:Hardcoded language list limits extensibility.

The languages array is hardcoded in the component. If more languages are added to the routing configuration (apps/dashboard/src/i18n/routing.ts), this list must be manually updated in sync.

Consider deriving the available languages from the routing configuration or a shared constants file:

// src/i18n/languages.tsexportconstlanguages=[{code:'en',name:'English',flag:'🇺🇸'},{code:'zh',name:'中文',flag:'🇨🇳'},]asconst;// Validate against routing config at build timeimport{routing}from'./routing';constlocaleSet=newSet(routing.locales);languages.forEach(lang=>{if(!localeSet.has(lang.code)){thrownewError(`Language${lang.code} not in routing config`);}});

Then import and use this shared constant in both the language switcher and any other components that need the language list.

apps/dashboard/src/i18n/request.ts (2)

16-16:Type assertions bypass type safety for locale validation.

The code usesas any type assertions when checking if the locale is included inrouting.locales. This bypasses TypeScript's type checking and could mask type mismatches.

Consider adding proper typing or using a type guard:

// In routing.ts, export locale typeexporttypeLocale=typeofrouting.locales[number];// In request.tsimport{routing,typeLocale}from'./routing';functionisValidLocale(locale:string):locale isLocale{returnrouting.locales.includes(localeasLocale);}// Then use:if(localeCookie&&isValidLocale(localeCookie.value)){locale=localeCookie.value;}if(!locale||!isValidLocale(locale)){locale=routing.defaultLocale;}

This provides better type safety and makes the intent clearer.

Also applies to: 22-22

---

26-29:Add error handling for missing locale message files.

The dynamic import at line 28 will throw an unhandled error if a locale's message file is missing or malformed. While this should not occur in production, it could cause issues during development or if the build process has problems.

Add error handling and a fallback:

try{return{      locale,messages:(awaitimport(`../../messages/${locale}.json`)).default};}catch(error){console.error(`Failed to load messages for locale "${locale}":`,error);// Fallback to default locale messagesreturn{locale:routing.defaultLocale,messages:(awaitimport(`../../messages/${routing.defaultLocale}.json`)).default};}

This prevents the entire app from crashing if a locale file is missing and provides a graceful degradation path.

scripts/fix-docker.sh (1)

1-105:Consider using English for script messages.

This script is part of an i18n PR focused on dashboard UI localization, yet the script itself uses Chinese-only messages. For developer tooling and scripts, English is the conventional choice to ensure wider accessibility and maintainability across international teams.

Apply this diff to replace Chinese messages with English:

-echo "🔧 Docker Desktop 修复工具"+echo "🔧 Docker Desktop Repair Tool" echo "================================" echo ""-# Step 1: 检查 Docker Desktop 状态-echo "📋 Step 1: 检查当前状态..."+# Step 1: Check Docker Desktop status+echo "📋 Step 1: Checking current status..." if pgrep -q "Docker Desktop"; then-    echo "   ✅ Docker Desktop UI 正在运行"+    echo "   ✅ Docker Desktop UI is running" else-    echo "   ❌ Docker Desktop UI 未运行"+    echo "   ❌ Docker Desktop UI is not running" fi if pgrep -q "com.docker.backend"; then-    echo "   ✅ Docker Backend 正在运行"+    echo "   ✅ Docker Backend is running"     echo ""-    echo "Docker 看起来正常，尝试连接..."-    docker ps > /dev/null 2>&1 && echo "   ✅ Docker 工作正常！" && exit 0+    echo "Docker appears healthy, attempting connection..."+    docker ps > /dev/null 2>&1 && echo "   ✅ Docker is working!" && exit 0 else-    echo "   ❌ Docker Backend 未运行（这是问题所在！）"+    echo "   ❌ Docker Backend is not running (this is the problem!)" fi echo ""-# Step 2: 完全停止 Docker-echo "📋 Step 2: 完全停止 Docker Desktop..."+# Step 2: Stop Docker completely+echo "📋 Step 2: Stopping Docker Desktop completely..." osascript -e 'quit app "Docker"' 2>/dev/null || true sleep 3-# 强制杀死所有 Docker 进程-echo "   → 清理残留进程..."+# Force kill all Docker processes+echo "   → Cleaning up remaining processes..." pkill -9 -f "Docker Desktop" 2>/dev/null || true pkill -9 -f "com.docker" 2>/dev/null || true sleep 2-# Step 3: 清理可能的锁文件-echo "📋 Step 3: 清理锁文件和状态..."+# Step 3: Clean potential lock files+echo "📋 Step 3: Cleaning lock files and state..." rm -f ~/Library/Group\ Containers/group.com.docker/docker.sock.lock 2>/dev/null || true rm -f ~/.docker/run/*.lock 2>/dev/null || true-echo "   ✅ 清理完成"+echo "   ✅ Cleanup complete" echo ""-# Step 4: 重启 Docker Desktop-echo "📋 Step 4: 重新启动 Docker Desktop..."+# Step 4: Restart Docker Desktop+echo "📋 Step 4: Restarting Docker Desktop..." open -a Docker-echo "   等待 Docker Desktop 启动..."+echo "   Waiting for Docker Desktop to start..." sleep 10-# 等待最多 60 秒让 Docker 完全启动-echo "   检查 Docker daemon 是否准备就绪..."+# Wait up to 60 seconds for Docker to fully start+echo "   Checking if Docker daemon is ready..." COUNTER=0 MAX_WAIT=60 while [ $COUNTER -lt $MAX_WAIT ]; do     if docker info > /dev/null 2>&1; then-        echo "   ✅ Docker daemon 已就绪！"+        echo "   ✅ Docker daemon is ready!"         break     fi          if pgrep -q "com.docker.backend"; then-        echo "   ⏳ Backend 进程已启动，等待就绪... ($COUNTER/$MAX_WAIT)"+        echo "   ⏳ Backend process started, waiting for ready... ($COUNTER/$MAX_WAIT)"     else-        echo "   ⏳ 等待 Backend 进程启动... ($COUNTER/$MAX_WAIT)"+        echo "   ⏳ Waiting for Backend process to start... ($COUNTER/$MAX_WAIT)"     fi          sleep 2     COUNTER=$((COUNTER + 2)) done echo ""-# Step 5: 验证-echo "📋 Step 5: 验证 Docker 状态..."+# Step 5: Verify+echo "📋 Step 5: Verifying Docker status..." if docker info > /dev/null 2>&1; then-    echo "   ✅ Docker 工作正常！"+    echo "   ✅ Docker is working!"     echo ""     docker version     echo ""     echo "================================"-    echo "✨ 修复成功！现在可以启动开发环境了："+    echo "✨ Repair successful! You can now start the dev environment:"     echo "   pnpm run start-deps:minimal"     echo "================================"     exit 0 else-    echo "   ❌ Docker 仍然无法连接"+    echo "   ❌ Docker still cannot connect"     echo ""     echo "================================"-    echo "⚠️  自动修复失败，请尝试："+    echo "⚠️  Auto-repair failed, please try:"     echo ""-    echo "1. 手动重启 Docker Desktop："-    echo "   - 点击菜单栏的 Docker 图标"-    echo "   - 选择 'Restart'"+    echo "1. Manually restart Docker Desktop:"+    echo "   - Click the Docker icon in the menu bar"+    echo "   - Select 'Restart'"     echo ""-    echo "2. 如果还不行，完全卸载重装："-    echo "   - 在 Docker Desktop 中选择 'Troubleshoot' > 'Clean / Purge data'"-    echo "   - 或者完全卸载后重新安装"+    echo "2. If that doesn't work, fully uninstall and reinstall:"+    echo "   - In Docker Desktop select 'Troubleshoot' > 'Clean / Purge data'"+    echo "   - Or completely uninstall and reinstall"     echo ""-    echo "3. 检查系统日志查看错误："+    echo "3. Check system logs for errors:"     echo "   tail -f ~/Library/Containers/com.docker.docker/Data/log/vm/dockerd.log"     echo "================================"     exit 1 fi

apps/dashboard/src/app/(main)/(protected)/projects/[projectId]/(overview)/metrics-page.tsx (1)

50-50:Simplify the namespace override for consistency.

The error message usest('globe.errorMessage', { ns: 'overview' }) with a namespace override. Since you're already in the'overview.metrics' namespace and there's aglobe.errorMessage key atoverview.metrics.globe.errorMessage in en.json, you can simplify this tot('globe.errorMessage') without the namespace override for better clarity and consistency.

Apply this diff:

-<ErrorBoundary fallback={<div className='text-center text-sm text-red-500'>{t('globe.errorMessage', { ns: 'overview' })}</div>}>+<ErrorBoundary fallback={<div className='text-center text-sm text-red-500'>{t('globe.errorMessage')}</div>}>

scripts/restart-dev-basic.sh (1)

24-34:Add a comment explaining the container count requirement.

The script checks for at least 7 running containers, but this number might be unclear to future maintainers. Adding a brief comment would improve clarity.

Apply this diff:

+# Minimal stack requires 7 containers: postgres, inbucket, svix, redis, etc. RUNNING_CONTAINERS=$(docker ps --filter "name=stack-dependencies" --format '{{.Names}}' | wc -l) if [ "$RUNNING_CONTAINERS" -lt 7 ]; then

packages/stack-ui/src/components/data-table/pagination.tsx (1)

13-17:Solid i18n extension with safe defaults; consider minor a11y tweak

Props and defaults look good. Optional: expose previous/next labels via aria-label on the Buttons (in addition to sr-only) for clearer accessible names.

-            <Button+            <Button               variant="outline"               className="h-8 w-8 p-0"               onClick={() => table.previousPage()}               disabled={!table.getCanPreviousPage()}+              aria-label={previousPageLabel}             >               <span className="sr-only">{previousPageLabel}</span>               <ChevronLeftIcon className="h-4 w-4" />             </Button>...-            <Button+            <Button               variant="outline"               className="h-8 w-8 p-0"               onClick={() => table.nextPage()}               disabled={!table.getCanNextPage()}+              aria-label={nextPageLabel}             >               <span className="sr-only">{nextPageLabel}</span>               <ChevronRightIcon className="h-4 w-4" />             </Button>

Also applies to: 21-25

apps/dashboard/src/app/(main)/(protected)/projects/[projectId]/emails/page-client.tsx (2)

321-341:Use next-intl formatter for locale-aware date/time

Leverage useFormatter for consistent i18n formatting.
Based on learnings

-import { useTranslations } from 'next-intl';+import { useTranslations, useFormatter } from 'next-intl';... const useEmailTableColumns = (): ColumnDef<AdminSentEmail>[] => {   const t = useTranslations('emails.emailLog.columns');+  const format = useFormatter();   return [     { accessorKey: 'recipient', header: t('recipient') },     { accessorKey: 'subject', header: t('subject') },     {-      accessorKey: 'sentAt', header: t('sentAt'), cell: ({ row }) => {-        const date = row.original.sentAt;-        return date.toLocaleDateString() + ' ' + date.toLocaleTimeString();-      }+      accessorKey: 'sentAt',+      header: t('sentAt'),+      cell: ({ row }) => format.dateTime(row.original.sentAt, { dateStyle: 'medium', timeStyle: 'short' })     },

Also applies to: 327-331

---

169-175:i18n gaps: several hard-coded strings remain

Multiple labels, titles, button texts, and descriptions are still hard-coded; convert to useTranslations for full i18n coverage.

Examples:

• Dialog titles/buttons: "Edit Email Server", "Save", "Send a Test Email", "Send", "Send Email", "Cancel", "Back", "Next".
• Field labels/options: "Email server", "Shared (noreply@stackframe.co)", "Resend ...", "Custom SMTP server ...", "Resend API Key", "Sender Email/Name", "Host/Port/Username/Password", "Notification Category", "Transactional/Marketing", "Email Content", "Subject".
• UI text: "Recipients", "Shared Email Server", "Warning", and the shared-server alert description.
• TeamMemberSearchTable action buttons: "Add"/"Remove".

If helpful, I can generate a targeted patch applying t('...') across these spots.

Also applies to: 221-229, 231-244, 247-264, 281-286, 314-314, 450-453, 498-510, 512-522, 551-552, 557-567, 569-574

apps/dashboard/src/components/data-table/team-table.tsx (1)

112-132:Type t for safer translations

Avoid any; type t to ReturnType (or a narrowed namespace type).

-const getColumns = (t: any): ColumnDef<ServerTeam>[] =>  [+const getColumns = (t: ReturnType<typeof useTranslations>): ColumnDef<ServerTeam>[] => [

apps/dashboard/src/app/(main)/(protected)/projects/[projectId]/(overview)/setup-page.tsx (1)

535-537:Localize Suspense fallback

"LOADING" is hard-coded; use a translated string.

-function GlobeIllustration() {+function GlobeIllustration() {+  const t = useTranslations('overview.setup');   return (     <div className="w-[200px] h-[200px] relative hidden md:block">-      <Suspense fallback={"LOADING"}>+      <Suspense fallback={t('loadingGlobe')}>         <GlobeIllustrationInner />       </Suspense>     </div>   ); }

apps/dashboard/src/app/(main)/(protected)/projects/[projectId]/sidebar-layout.tsx (1)

585-587:Optional: i18n for "Sidebar Menu"

Translate SheetTitle to align with the rest of the navigation texts.

-  <SheetTitle className="hidden">-    Sidebar Menu-  </SheetTitle>+  <SheetTitle className="hidden">+    {t('sidebarMenu')}+  </SheetTitle>

scripts/kill-dev-servers.sh (4)

1-4:Enable strict mode and pipefail for safer execution

Prevents silent failures and masked pipeline errors; add ERR traps if desired.

 #!/bin/bash++# Fail fast and catch pipeline errors+set -Eeuo pipefail+# Optional: basic trap+trap 'echo "kill-dev-servers aborted"; exit 1' ERR

---

12-29:Fix SC2155 and quote vars in kill_process_tree

Avoids masking return values and handles PIDs with defensive quoting. Based on static analysis hints.

 kill_process_tree() {-    local pid=$1-    local sig=${2:-TERM}+    local pid+    pid="$1"+    local sig+    sig="${2:-TERM}"@@-    local children=$(pgrep -P $pid 2>/dev/null)+    local children+    children=$(pgrep -P "$pid" 2>/dev/null || true)@@-        kill_process_tree $child $sig+        kill_process_tree "$child" "$sig"@@-    if kill -0 $pid 2>/dev/null; then-        kill -$sig $pid 2>/dev/null || true+    if kill -0 "$pid" 2>/dev/null; then+        kill -"${sig}" "$pid" 2>/dev/null || true     fi }

---

68-89:Use graceful tree kill before -9 on port PIDs

Blind kill -9 risks leaving children/orphans. Reuse kill_process_tree with TERM then KILL.

 for port in "${DEV_PORTS[@]}"; do   pids=$(lsof -ti:$port 2>/dev/null)   if [ ! -z "$pids" ]; then     echo "    ✓ Killing processes on port $port"-    echo "$pids" | xargs kill -9 2>/dev/null || true+    for pid in $pids; do+      kill_process_tree "$pid" TERM+      sleep 0.3+      # Ensure termination if still alive+      kill_process_tree "$pid" KILL+    done   fi done@@   for port in "${DOCKER_PORTS[@]}"; do     pids=$(lsof -ti:$port 2>/dev/null)     if [ ! -z "$pids" ]; then       echo "    ✓ Killing processes on port $port"-      echo "$pids" | xargs kill -9 2>/dev/null || true+      for pid in $pids; do+        kill_process_tree "$pid" TERM+        sleep 0.3+        kill_process_tree "$pid" KILL+      done     fi   done

---

91-93:Remove unused ALL_PORTS variable

SC2034: variable is never used.

-# Combine all ports for verification-ALL_PORTS=("${DEV_PORTS[@]}" "${DOCKER_PORTS[@]}")

scripts/start-dev.sh (2)

1-4:Harden script with pipefail and traps

Prevents masked failures (esp. pipelines) and improves resiliency.

 #!/bin/bash-set -e  # Exit on any error+set -Eeuo pipefail  # Exit on errors, unset vars, and pipeline failures+# Optional: trap failures for cleanup/log+trap 'echo "start-dev aborted"; exit 1' ERR

---

46-47:Pipeline masks errors from kill script

With tail, failures in kill-dev-servers.sh won’t fail this step unless pipefail is set. Either set pipefail (above) or avoid piping.

-bash "$(dirname "$0")/kill-dev-servers.sh" | tail -n 5+if ! bash "$(dirname "$0")/kill-dev-servers.sh"; then+  echo "❌ Failed to clean up dev servers"; exit 1+fi

apps/dashboard/src/components/data-table/api-key-table.tsx (1)

12-22:Consider i18n for DataTableFacetedFilter internal strings

Faceted filter currently renders “No results found.” and “Clear filters” in English (see packages/stack-ui/.../faceted-filter.tsx). Add i18n props there and pass translations here.

packages/stack-ui/src/components/data-table/data-table.tsx (1)

46-135:Consider adding i18n support for the "No results." string.

The i18n prop is correctly propagated toDataTableToolbar andDataTablePagination. However, the hardcoded "No results." string at line 119 is not exposed through the i18n interface.

To fully internationalize the component, add anoResults field toDataTableI18n:

 export type DataTableI18n = {   resetFilters?: string,   exportCSV?: string,   noDataToExport?: string,   view?: string,   toggleColumns?: string,   rowsSelected?: (selected: number, total: number) => string,   rowsPerPage?: string,   previousPage?: string,   nextPage?: string,+  noResults?: string, };

Then update line 119:

-                  No results.+                  {props.i18n?.noResults || "No results."}