add v10 next-prisma-starter-websockets example #2683
Closed
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.
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)