GPT-5 finding
Possible hydration mismatch risk from using Number.toLocaleString() without a fixed locale
mediumbughigh
- apps/web/app/activity/ActivityView.tsx
Client components are server-rendered in Next.js. Number.toLocaleString() without an explicit locale may format differently between server and client environments (e.g., comma vs dot thousands separator), causing hydration mismatch warnings and visible flicker. The file explicitly avoids date mismatches but leaves number formatting locale-dependent.
Recommendation
Use a deterministic formatter across SSR and client, e.g., Intl.NumberFormat('en-US').format(value), or pass preformatted strings from the server. Alternatively, explicitly pass a fixed locale to toLocaleString, e.g., value.toLocaleString('en-US').