fix(config): resolve Next.js 15 transpilePackages conflict with serverExternalPackages

- Removed recharts, framer-motion, and motion from serverExternalPackages in next.config.ts
- Removed same UI libs from external_node_modules in netlify.toml
- These client-only UI libraries were conflicting with Next.js transpilation
- Kept server-side packages (OpenAI, Stripe, Sentry, Supabase, etc.) externalized
- Build now completes successfully (exit code 0)
- Resolves Netlify build error: 'packages in transpilePackages conflict with serverExternalPackages'

Validation:
✅ Type check passes (tsc --noEmit)
✅ Lint passes (only warnings, no errors)
✅ Production build succeeds (npm run build)
✅ Static generation: 76/76 pages
✅ First Load JS optimized with proper chunking

Author: apex-ai-net

netlify.toml

@@ -61,6 +61,8 @@
 
   # Externalize large packages - they'll be available at runtime
   # but not bundled into the Lambda function
+  # Note: Only server-side packages should be externalized to avoid conflicts
+  # with Next.js transpilePackages (client UI libs are bundled normally)
   external_node_modules = [
     "@sentry/nextjs",
     "@sentry/node",
@@ -72,9 +74,6 @@
     "@supabase/supabase-js",
     "@supabase/auth-helpers-nextjs",
     "svix",
-    "pg",
-    "recharts",
-    "framer-motion",
-    "motion"
+    "pg"
   ]
 

next.config.ts

@@ -23,10 +23,8 @@ const nextConfig: NextConfig = {
     '@supabase/supabase-js',
     '@supabase/auth-helpers-nextjs',
     'pg',
-    // Large UI/Animation libraries
-    'recharts',
-    'framer-motion',
-    'motion',
+    // UI/Animation libraries removed - they conflict with transpilePackages in Next.js 15
+    // Removed: 'recharts', 'framer-motion', 'motion'
   ],
   outputFileTracingRoot: path.join(__dirname),
   // Expose Sentry DSN to the client without adding new Netlify vars