[Docs] Document Supabase Missing Environment Variable Troubleshooting
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5
- Forks
- 7
- Avg merge
- 39m
- Merged PRs (30d)
- 39
Description
Target File
docs/TROUBLESHOOTING.md
Estimated Time
5-10 minutes
Difficulty
Level 1 (Beginner)
Why This Matters
Developers setting up PACT locally may occasionally forget to copy .env.example to .env.local, causing runtime Supabase client initialization errors.
Current Behavior
docs/TROUBLESHOOTING.md covers RLS recursion and Node versions, but lacks a dedicated section for missing Supabase URL/Key environment variables.
Requested Change
Add a subsection under Section 3 (Environment Variables) in docs/TROUBLESHOOTING.md detailing Symptom, Cause, and Fix.
Acceptance Criteria
- Subsection added with clear Symptom, Cause, and Fix matching existing document style.
- Passes link audit via node scratch/check-links.mjs.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Open docs/TROUBLESHOOTING.md and review Section 3 (Environment Variables) and its existing style. Add a subsection covering the missing Supabase URL/key symptom, cause, and fix, then run node scratch/check-links.mjs. Done means the subsection is clear, matches the document style, and passes the link audit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, supabase
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 95/100