Skip to content

resolve async queries before passing to SWR fallback and update Stripe API#271

Open
mohamed-benoughidene wants to merge 5 commits into
nextjs:mainfrom
mohamed-benoughidene:fix/swr-config-and-stripe-api
Open

resolve async queries before passing to SWR fallback and update Stripe API#271
mohamed-benoughidene wants to merge 5 commits into
nextjs:mainfrom
mohamed-benoughidene:fix/swr-config-and-stripe-api

Conversation

@mohamed-benoughidene

Copy link
Copy Markdown

Summary:

  • Await getUser() and getTeamForUser() in RootLayout to avoid passing unresolved promises to SWRConfig fallback (Next.js 15 hydration fix)
  • Update Stripe API version from 2025-04-30.basil to 2025-08-27.basil

Problem :

  1. Invalid SWR Configuration: Next.js 15 requires resolved data in SWRConfig.fallback, not unresolved promises. Passing promises caused hydration mismatches.
  2. Stripe API Version: The Stripe SDK expected 2025-08-27.basil but the code used outdated 2025-04-30.basil, causing TypeScript build failure.

Files Changed:

  • app/layout.tsx - Made RootLayout async, awaited queries
  • lib/payments/stripe.ts - Updated API version

…Stripe API version

- Await getUser() and getTeamForUser() in RootLayout to avoid passing
  unresolved promises to SWRConfig fallback (Next.js 15 hydration fix)
- Update Stripe API version from 2025-04-30.basil to 2025-08-27.basil
@vercel

vercel Bot commented Apr 17, 2026

Copy link
Copy Markdown

@mohamed-benoughidene is attempting to deploy a commit to the Vercel Team on Vercel.

A member of the Team first needs to authorize it.

Comment thread app/(login)/actions.ts Outdated
Co-authored-by: vercel[bot] <35613825+vercel[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant