Module not found errors on Vercel deployment with shadcn-ui and custom tsconfig.json paths #3683
Replies: 3 comments 2 replies
-
Did you find a fix for this i got the same |
Beta Was this translation helpful? Give feedback.
-
Hi, I hope you're all doing well. I faced a similar issue when deploying Shadcn UI components. The problem occurred because I renamed or restructured the components. It wasn't just the renaming or restructuring itself, but rather the fact that I used PascalCase for the filenames. Since Vercel's Linux environment is case-sensitive, this caused issues. A good solution is to rename all the component files to lowercase, or alternatively, you can customize the |
Beta Was this translation helpful? Give feedback.
-
I ran the same error and found that lib director was excluded from git in |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Body:
I'm encountering issues deploying my Next.js project to Vercel where multiple "Module not found" errors appear, despite everything working perfectly in my local environment. This project utilizes
shadcn-ui
, and I suspect there may be complications related to path aliases in mytsconfig.json
that are not being resolved correctly on Vercel.File Structure:
tsconfig.json
Configuration:Error Messages on Vercel:
I would appreciate any help to understand why these path aliases might not be working on Vercel, particularly with my usage of
shadcn-ui
. Any insights or similar experiences would be really helpful!Beta Was this translation helpful? Give feedback.
All reactions