Modernize to Next.js 15 and update all dependencies #2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Update Next.js 14 -> 15 with async params/searchParams - Update Supabase SSR 0.1.0 -> 0.5.2 - Update Stripe SDK and modernize API usage - Fix all TypeScript errors and linting issues - Update all dependencies to latest versions - Add ESLint configuration - Remove pnpm-lock.yaml (template repo best practice) - Resolve security vulnerabilities (0 vulnerabilities)
SamRome1
added
documentation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce?
This is a fork of the current deprecated Stripe, Vercel starter kit on the Supabase main page if you scroll down. It is a modernization due to it not being up kept resulting in new feature updates, dependency modernization, and documentation update to mimic the correct behavior.
What is the current behavior?
The template uses outdated dependencies:
What is the new behavior?
Additional context
Future-proofing note: Once Next 16 is more battle-tested in the ecosystem (and the template’s dependencies/patterns are validated against it), we can do a follow-up PR to bump to 16.x with a tighter scope.