Modernize to Next.js 15 and update all dependencies #2
Conversation
- 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
There was a problem hiding this comment.
@SamRome1 Thanks for this update!
I know we talked about it in the meeting a little, but do you think it makes sense to update it to use Next.js v16? I think having the latest version just makes it more marketable!
Actually, let's upgrade it to v16 in another PR. This PR is complete with the current state. Let me take a quick look.
There was a problem hiding this comment.
Just curious, why was this deleted?
There was a problem hiding this comment.
I was running into problems with the existing lock file contents. The lock file contains resolved dependency trees based on the old versions, and when you're updating dependencies from older versions (like Supabase SSR 0.1.0 → 0.5.2 and Next.js 14 → 15.1.3), you run into issues because you can't easily change the whole dependency tree. Also, when users clone the starter kit and run pnpm install, it will create a fresh lock file for them anyway.
|
Thanks for this update! It's great! Feel free to merge it! |
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.