I’m hoping someone here has had a similar issue and knows of a solution… My project builds and deploys on all pre-production branches no problem. Dev, Test, and all previews, all good. But when I tried to do a Production release, it fails to build with errors with not able to find my UI modules (tailwind/shadCN). One thing I noticed as well was during the build, it installs almost 200 less packages? I’m at my wits end, I’ve tried not using a cached install, renaming the components package incase it was a case sensitive issue, using direct path instead of alias. Not sure what else I can do…
Does your package.json look right? Have you tried deleting your node-modules folder and your lockfile if you have one and reinstalling?
AFAIK the package.json looks accurate, I even moved a bunch of the packages to dependencies instead of just devDependencies to see if that was the case. I’ve deleted my node_modules, lock file, and did a npm cache clean --force before installing multiple times. Nothing I do seems to be working. What’s also very strange to me is that it’s only an issue with the production release from main branch build. All other branches and builds are installing all the packages but the main just refuses to.
Also local builds work fine. All builds from local to all pre-production release branches, all work.
I even merged the main branch back into test branch to see what happens, and it built and deployed just fine… This is driving me insane
Hmm. What happens if you create a new prod deployment from within the vercel dashboard?
same issue, doesn’t install all the packages, fails the build
using the vercel CLI, and I see the same kinda result. Preview branches work fine off the same branch+commit. But production says no go…
I figured it out… It has to do with either the new Next.js or Vercel CLI with how they build production deployments. It required that all “dev dependencies” to be actual dependencies… which is strange as heck… That has to be a bug of some sort.
1 Like
Hmm yeah curious what did you have marked down as dev dependencies vs production ones? Glad you got it figured out though!
Would this also affect openai API stuff?
My app uses the api to generate some things but fails at others when they’re really similar.
Thanks in advance
Hey,
Make sure the components folder is uploaded to GitHub as well and also make sure that it doesn’t exist and comment in .gitignore, remove it from .gitignore
Not too sure, I think it’s related to whatever you have under your dev dependencies at the moment. I logged an issue with vercel on github about it.
Yea, all my folders are commited and not in the gitignore, i know it’s not just the components as it also doesn’t install TRPC with my project.