⚖MikeWatch Forks of the Mike legal-AI codebase, distilled for legal-tech readers
Home · juanjo/mike · this thread

Supabase packages uninstalled, env vars cleaned up, docs updated

Three commits close out Plan 2: the Supabase npm packages are removed from both frontend and backend, env example files drop the `SUPABASE_*` vars, and new Serena memory files document the post-migration codebase shape. After this sequence the fork has no Supabase code paths.

infrastructure

511c8e7 does the main teardown. backend/src/lib/supabase.ts is deleted (it had no remaining importers). @supabase/supabase-js is uninstalled from the backend; @supabase/{supabase-js,auth-helpers-nextjs,auth-js} are uninstalled from the frontend. backend/migrations/000_one_shot_schema.sql gets a DEPRECATED header pointing at the Drizzle migration files. The README setup section is rewritten to match the new Docker-based workflow.

74e9d7c strips SUPABASE_URL, SUPABASE_SECRET_KEY, and NEXT_PUBLIC_SUPABASE_* from both .env.example files and removes a stale fallback in downloadTokens.ts that was using SUPABASE_SECRET_KEY as a fallback signing secret (it now falls back to AUTH_SECRET instead).

9e099c9 adds two Serena memory files. codebase_structure.md is the most useful: it maps the full file tree for both backend and frontend, and calls out the dual components/, lib/, and contexts/ directories on the frontend as a known gotcha. task_completion_checklist.md documents that the project has no test suite - verification is npm run build on both packages plus npm run lint on the frontend, then manual browser exercise for UI changes.

This is a state marker more than a feature. The README and Serena files are reusable independently; the package removals only make sense behind the full migration chain.

So what Skip as a standalone import - it breaks the build without the preceding migration chain. The README rewrite and `codebase_structure.md` Serena memory are worth reading for their documentation of the post-migration file layout and dual-directory conventions.

View this fork on GitHub →

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?

Commits in this thread

3 commits from juanjo/mike, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
511c8e7e chore: uninstall Supabase, deprecate legacy schema, update docs (Plan 2 complete) Juan Vidal 2026-05-08 ↗ GitHub
commit body 
- git rm backend/src/lib/supabase.ts (no remaining importers)
- npm uninstall @supabase/supabase-js from backend
- npm uninstall @supabase/supabase-js @supabase/auth-helpers-nextjs @supabase/auth-js from frontend
- Add DEPRECATED header to backend/migrations/000_one_shot_schema.sql
- Update README.md: Supabase → Postgres/Drizzle setup instructions
- Update .serena/memories: reflect Plan 1 + Plan 2 both complete

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
74e9d7c2 chore: drop stale Supabase env vars from .env.example and downloadTokens fallback Juan Vidal 2026-05-08 ↗ GitHub 
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
9e099c90 docs(serena): scrub remaining Supabase references from memories Juan Vidal 2026-05-08 ↗ GitHub 
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-186.md from inside the repo you want the changes in.

⬇ Download capture-thread-186.md