fix(api): fix vercel cache for prisma generated #76
Conversation
This file contains 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
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
TL;DR
Updated the build script in
package.jsonto includeprisma generatebefore runningnext build. Kudos to https://www.prisma.io/docs/orm/more/help-and-troubleshooting/help-articles/vercel-caching-issueWhat changed?
Modified the build script in the
package.jsonfile fromnext buildtoprisma generate && next build.How to test?
Run the build script using
npm run buildand ensure that Prisma client is generated before the Next.js build process is initiated.Why make this change?
This change ensures that the Prisma client is always up-to-date before building the Next.js application, preventing potential runtime issues related to the database schema.