📝 Vercel monorepo deployment (no public page) 6 commits 11d ago not yet rewritten
NavpreetSSidhu/mike
NavpreetSSidhu's fork of Mike is in the wiring-up phase, focused on getting the app live on Vercel rather than reshaping the product.
This is an early-stage fork of Mike from NavpreetSSidhu, and what's visible so far is plumbing rather than product. The bulk of the activity is a hands-on push to get both halves of Mike - the Next.js frontend and the Express backend - deployed together on Vercel, working through the usual monorepo friction one failure at a time.
Alongside the deployment work, there's a small defensive hardening pass on the backend so unhandled errors are caught and logged instead of taking the process down silently.
There's no rebrand, no narrowed legal niche, and no shift in audience yet. If you're curious whether NavpreetSSidhu is heading somewhere specific with this fork, it's too early to tell from the work itself - this looks like someone standing the app up on their own infrastructure before deciding what to build on top.
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
📝 Backend global error handlers (no public page) 1 commit 11d ago not yet rewritten