Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

/submit, /my-list, and /onboarding return 500 when Supabase isn't configured

Open Beginner friendly
#127 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@Aryan-Techie is already working on this.

Since Oct 22, 2026.

  • #128 by @Aryan-Techie — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
75/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
next.js, node.js, supabase, typescript

Research direction

Start with the /submit, /my-list, and /onboarding page entry points and compare how they create a Supabase client with the mock-data fallbacks used elsewhere. Check the behavior after #124 for reference. Done means these routes show a clear message when Supabase credentials are absent, while retaining their current behavior with credentials; verify both cases using the reproduction steps in the issue.

Written by the indexing model from the issue text.

Description

Route

/submit, /my-list, /onboarding

Steps to reproduce

  1. Fresh checkout of main, no .env.local (this is how CONTRIBUTING.md suggests trying the app before setting up Supabase).
  2. pnpm dev
  3. Open /submit, /my-list, or /onboarding.

Actual behavior

Each page returns 500 with Your project's URL and Key are required to create a Supabase client!. The pages create a Supabase client while rendering. Everything else falls back to mock data without credentials: the directory, deadlines, the API routes, and after #124 the proxy and /admin.

Expected behavior

Without Supabase configured, these pages render a clear message that sign-in isn't available in this environment, instead of crashing. Behavior with credentials stays the same.

Dominant language
TypeScript
Stars
1
Forks
6
Avg merge
22h 9m
Merged PRs (30d)
42

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Your-Voldemort/StudentStack

All issues in Your-Voldemort/StudentStack

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.