NavpreetSSidhu/mike

Vercel monorepo deployment with esbuild bundling and lazy Supabase client

Two topics: global error handlers added to the Express backend (`process.on('unhandledRejection')` and `uncaughtException`), and a Vercel monorepo deployment path built across six commits - switching the backend build from `tsc` to esbuild, exporting the app as a default for serverless, and vendoring a pre-bundled `@google/genai` to bypass Vercel's nft module tracer.

View on GitHub →

NavpreetSSidhu's fork focuses on getting mike deployed to Vercel as a monorepo. The work covers two areas: basic process hardening (global error handlers in the Express backend) and a multi-commit Vercel deployment setup that required an esbuild migration, a vendored @google/genai bundle to work around nft tracer bugs, and a lazy Supabase client proxy to prevent Next.js SSR crashes.

What's in it

Vercel deployment of the full stack Frontend and backend are being wired up to deploy together on Vercel, with the monorepo quirks worked through commit by commit.
Backend error resilience Unhandled errors and rejections at the process level are now caught and logged so the backend fails more predictably.

Direction

infrastructure

Activity

Themed changes and pull requests touching this fork, newest first. Themed changes that haven't been turned into a public post yet still appear — they're real work even without a published writeup.

📝 NavpreetSSidhu is wrestling Mike onto Vercel 6 commits 2mo ago infrastructure draft

Six commits to get the whole fork running on a mainstream hosting platform - most of them spent fighting the platform's own build tooling.

📝 Backend global error handlers 1 commit 2mo ago minor change

Threads of work (detailed view)

1 thread have been distilled into posts.

NavpreetSSidhu is wrestling Mike onto Vercel

Six commits to get the whole fork running on a mainstream hosting platform - most of them spent fighting the platform's own build tooling.

infrastructure

6 commits · latest 2mo ago