Update Prisma to v5.1.1 and define Node.js 18 LTS as the minimum #221
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.
Once every often I have come across the issue where the Prisma client dependency has not been found, even after it was specifically generated.
Looking at
node_modules/@prisma/client
prisma/prisma#17162...got the idea to define where the generated client should go.
Before
npx prisma generate
:Environment variables loaded from .env
Environment variables loaded from prisma/.env
Prisma schema loaded from prisma/schema.prisma
✔ Generated Prisma Client (5.1.1 | library) to ./prisma/node_modules/@prisma/client in 218ms
You can now start using Prisma Client in your code. Reference: https://pris.ly/d/client
After
npx prisma generate
:Environment variables loaded from .env
Environment variables loaded from prisma/.env
Prisma schema loaded from prisma/schema.prisma
✔ Generated Prisma Client (5.1.1 | library) to ./node_modules/.prisma/client in 223ms
You can now start using Prisma Client in your code. Reference: https://pris.ly/d/client
But then reverted
Since there were issues with Docker builds and since "it works most of the time", I gave it a rest.