fix: prisma folder name#1039
Merged
Merged
Conversation
Klakurka
approved these changes
Aug 14, 2025
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Related to #
Description
For some reason,
import X from 'prisma/Y'started being interpreted as "import X from the node moduleprismafolderY" instead of "import X from our repo folderprisma/Y" , i.e., the same as if it wereimport X from '@prisma/Y'(notice the@).Since this happened when deploying production, and since I didn't see any mention of this when looking into the prisma github repo issues & their changelogs, I just assumed it was some side-effect and decided to just rename our
prismafolder toprisma-local.Test plan
N/A, everything should just work as before.