🚨 CRITICAL FIX: Remove webpack externals causing require() errors

[codeunia-dev]

🚨 Critical Issue Fixed

• ✅ Remove problematic webpack externals configuration
• ✅ Fix 'require is not defined' errors in browser
• ✅ Prevent Node.js modules from being bundled for client-side
• ✅ Restore website functionality

🎯 Root Cause

• webpack externals were causing Supabase modules to be excluded incorrectly
• This led to 'require is not defined' errors in the browser
• Website was completely broken with 'Something went wrong' error

📊 Results

• ✅ Website should now load properly
• ✅ No more 'require is not defined' errors
• ✅ Supabase client should work correctly in browser
• ✅ Edge Runtime compatibility maintained

Summary by CodeRabbit

• Bug Fixes
  • Resolved occasional client-side errors related to Node-specific modules in the browser, improving reliability across pages that use these features.
• Chores
  • Updated client build configuration to better handle browser environments and avoid unnecessary polyfills.
  • Simplified dependency handling by bundling certain libraries directly instead of externalizing them, reducing configuration complexity and potential integration issues.
  • Overall, improves stability and predictability of the web app in client contexts without changing user-facing functionality.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
codeunia	Building	Preview	Comment	Sep 12, 2025 2:29pm

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

Client-side webpack config now sets resolve.fallback for net, tls, and crypto to false (alongside fs). Removal of client-side externals for '@supabase/supabase-js' and '@supabase/ssr' means these packages are no longer externalized and will be bundled normally.

Changes

Cohort / File(s)	Summary
Build config adjustments next.config.ts	Added config.resolve.fallback entries: net: false, tls: false, crypto: false (keeping fs: false). Removed code that pushed @supabase/supabase-js and @supabase/ssr into config.externals for client builds, so these libraries are now bundled rather than externalized.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

I thump my paws at build-time cheer,
No externals now—bring Supabase near!
Net, tls, crypto set to no,
The bundle hops where modules go.
In leafy logs, I twirl my ear—
Config is tidy, the path is clear. 🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 53aadfe and d6a6219.

📒 Files selected for processing (1)

• next.config.ts (1 hunks)

✨ Finishing touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/ci-cd-pipeline-and-performance-optimizations

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}