Latest

While helping the Cal.com team, I resolved a critical issue where Sentry’s Next.js integration caused Vercel builds to run out of memory. The root cause was the `withSentryConfig()` wrapper bloating server-side output during build. By removing it and replacing it with a lightweight `@sentry/cli` script for client-side source maps, we restored stable, fast, and memory-efficient builds—without losing Sentry’s error tracking.

2 nights...