New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add v10 next-prisma-starter-websockets example #2685
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great, but CI takes a while (#2528) and I gotta run now. Will merge when I get back and add this test to branch protection settings.
Thank you so much! If you setup github sponsors I'll send you some $$$ :)
Relates to #2152
🎯 Changes
Add a full v10 port (no interop) of the next-prisma-starter-websockets example
Builds, passes lint and test, and works fine based on some quick manual testing.
I locked the version of
next
to12.2.5
for the time being as there is a type error on the AppRouter until this gets merged into main: vercel/next.js#40391Once that happens, it should be fine to upgrade to
^12.3.1
or similar.Also currently the folder name is
next-prisma-starter-websockets
but the name in package.json isnext-starter-websockets
. This is how it was in the existing interop example, let me know if you want me to make it consistent, and to what :)✅ Checklist
(no tests needed changing)