Need assistance diagnosing a final client-side execution failure or Vercel Edge hydration conflict.
Unanswered
Pip gall wasp posted this in #help-forum
Pip gall waspOP
I have exhausted all standard troubleshooting methods for a critical production error. My project is experiencing a silent client-side execution freeze on the login form after resolving a severe Middleware Redirect Loop.
Goal: Need assistance diagnosing a final client-side execution failure or Vercel Edge hydration conflict.
Project/Setup: Next.js 14 (App Router) + Supabase (Auth/Postgres) on Vercel.
Full Troubleshooting History (The Bug Chain):
Resolved: All 39 initial TypeScript/never errors were resolved by typing Supabase client factories.
Resolved: All Build Errors (@supabase/realtime-js module not found) were resolved by implementing dynamic imports (useEffect / ssr: false).
Resolved: The Middleware Redirect Loop was debugged and fixed by:
Setting Vercel ENV: AUTH_COOKIE_DOMAIN=.vercel.app, NEXT_PUBLIC_SITE_URL.
Implementing server-side session sync in /auth/session.
Current, Final Error (The Code Freeze):
Symptom: The Login form's submit button is completely dead (no animation, no network request, no console error).
Context: The form uses a standard onSubmit={handleSubmit} handler. All attempts to debug the event listener's connection have failed. The application is frozen because the client-side JavaScript is not executing the event handler.
Request: Has anyone encountered a scenario where the combination of nookies / Supabase auth sync / App Router middleware causes a silent, fatal event handler freeze on the client side, despite a successful build?
Goal: Need assistance diagnosing a final client-side execution failure or Vercel Edge hydration conflict.
Project/Setup: Next.js 14 (App Router) + Supabase (Auth/Postgres) on Vercel.
Full Troubleshooting History (The Bug Chain):
Resolved: All 39 initial TypeScript/never errors were resolved by typing Supabase client factories.
Resolved: All Build Errors (@supabase/realtime-js module not found) were resolved by implementing dynamic imports (useEffect / ssr: false).
Resolved: The Middleware Redirect Loop was debugged and fixed by:
Setting Vercel ENV: AUTH_COOKIE_DOMAIN=.vercel.app, NEXT_PUBLIC_SITE_URL.
Implementing server-side session sync in /auth/session.
Current, Final Error (The Code Freeze):
Symptom: The Login form's submit button is completely dead (no animation, no network request, no console error).
Context: The form uses a standard onSubmit={handleSubmit} handler. All attempts to debug the event listener's connection have failed. The application is frozen because the client-side JavaScript is not executing the event handler.
Request: Has anyone encountered a scenario where the combination of nookies / Supabase auth sync / App Router middleware causes a silent, fatal event handler freeze on the client side, despite a successful build?