Issue Station
Sign In
Tools hereToolbox

nextjs - ✅(Solved) Fix Docs: with-supabase README references wrong env variable name [2 pull requests, 4 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
vercel/next.js#84734•Fetched 2026-04-08 02:18:41
View on GitHub
Comments
4
Participants
3
Timeline
15
Reactions
0
Author
CarloQuickCarloQuick
Participants
CarloQuickCarloQuickgithub-actions[bot]github-actions[bot]icyJosephicyJoseph
Timeline (top)
commented ×4cross-referenced ×2mentioned ×2subscribed ×2

Fix Action

Fixed

PR fix notes

PR #1: [docs] fix with-supabase README env variables

Description (problem / solution / changelog)

Closes #84734

Fixes environmental variable names in with-supabase example README to match the actual .env.example file.

Updates NEXT_PUBLIC_SUPABASE_ANON_KEY to NEXT_PUBLIC_SUPABASE_PUBLISHABLE_OR_ANON_KEY in two locations.

Changed files

  • examples/with-supabase/README.md (modified, +2/-2)

PR #84745: [docs] fix(with-supabase): Update README env variables

Description (problem / solution / changelog)

Closes #84734

Fixes environmental variable names in with-supabase example README to match the actual .env.example file.

Updates NEXT_PUBLIC_SUPABASE_ANON_KEY to NEXT_PUBLIC_SUPABASE_PUBLISHABLE_OR_ANON_KEY in two locations.

Changed files

  • examples/with-supabase/.env.example (modified, +1/-1)
  • examples/with-supabase/README.md (modified, +10/-6)
  • examples/with-supabase/lib/supabase/client.ts (modified, +1/-1)
  • examples/with-supabase/lib/supabase/middleware.ts (modified, +1/-1)
  • examples/with-supabase/lib/supabase/server.ts (modified, +1/-1)
  • examples/with-supabase/lib/utils.ts (modified, +1/-1)
RAW_BUFFERClick to expand / collapse

What is the documentation issue?

In the with-supabase example, Section 4 of the README.md refers to environmental variable NEXT_PUBLIC_SUPABASE_ANON_KEY, but the actual variable in .env.example is NEXT_PUBLIC_SUPABASE_PUBLISHABLE_OR_ANON_KEY.

Is there any context that might help us understand?

Following the Next.js quick start at https://supabase.com/docs/guides/getting-started/quickstarts/nextjs, I found environmental variable differences between the tutorial and this example.

NEXT_PUBLIC_SUPABASE_PUBLISHABLE_OR_ANON_KEY is the correct variable used in this example. This may cause confusion to developers getting started with the example.

Does the docs page already exist? Please link to it.

https://github.com/vercel/next.js/blob/canary/examples/with-supabase/README.md

Happy to submit a PR to fix this if helpful.

extent analysis

TL;DR

Update the README.md in the with-supabase example to refer to the correct environmental variable NEXT_PUBLIC_SUPABASE_PUBLISHABLE_OR_ANON_KEY.

Guidance

  • Verify the environmental variable name in .env.example to ensure it matches the one used in the code.
  • Check the Next.js quick start guide at https://supabase.com/docs/guides/getting-started/quickstarts/nextjs for any updates or corrections to environmental variable names.
  • Update the README.md file to reflect the correct environmental variable name to avoid confusion for developers getting started with the example.
  • Consider submitting a PR to fix this documentation issue, as offered.

Example

No code snippet is necessary for this documentation fix.

Notes

This fix assumes that the correct environmental variable name is indeed NEXT_PUBLIC_SUPABASE_PUBLISHABLE_OR_ANON_KEY, as stated in the issue.

Recommendation

Apply workaround: Update the README.md to refer to the correct environmental variable NEXT_PUBLIC_SUPABASE_PUBLISHABLE_OR_ANON_KEY, as this is a documentation issue that can be resolved with a simple correction.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#file not found#serialization error#model compatibility#GPU setup#container setup

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING