Error: Command "pnpm run build" exited with SIGABRT
Unanswered
Kishu posted this in #help-forum
KishuOP
Build failed in vercel deployment, thowing an error: "Error: Command "pnpm run build" exited with SIGABRT".
I am able to run the build successfully in my local environment, but not able to build in vercel deployment.
First I tried with npm, got the build error, so tried with pnpm, still getting the build error.
I have attached my build log from vercel as a screenshot to this post. I have no idea why this error occurs...
I am able to run the build successfully in my local environment, but not able to build in vercel deployment.
First I tried with npm, got the build error, so tried with pnpm, still getting the build error.
I have attached my build log from vercel as a screenshot to this post. I have no idea why this error occurs...
25 Replies
have you tried to clear the cache and build again?
KishuOP
Yes, I tried to clear the cache by leaving option unchecked and then redeployed it, but still got the same error.....
try create a new project and see if it builds?
KishuOP
Okay, I deleted my project and created a new project and deployed it... still fails...
😵
KishuOP
But I am able to build the project on my local environment.
Does my build fails due to the size of the files that are statically generated ?
not sure, can you try to remove some import on the page
/writeups/[writeup] and try deploy again?or use dynamic import and see if it helps
KishuOP
okay
I am using plaiceholder to fetch images to use with next/image, which is implemented in /writeups/[writeup] , will that be a issue?
what package do you use?
try put
plaiceholder to serverComponentsExternalPackagesKishuOP
you generating in the server component right?
KishuOP
yes
Gitihub Repo for your reference: https://github.dev/Thamizhiniyan18/Portfolio
KishuOP
Okay I tired it but, still fails
try
plaiceholderKishuOP
okay
still failed
is there any place where i could see a more detailed error .... the above error is not so detailed
KishuOP
Actually I think this is an bug with Vercel. I was able to successfully deploy the same repository with netlify with no errors..