Since today, my deploys on Vercel have started failing with errors that didn’t appear yesterday (yesterday I was able to deploy without issues). The build log shows messages like:
Module not found: Can't resolve '.../lucide-react/dist/esm/icons/pen-square'
Error: To use Server Actions, please enable the feature flag in your Next.js config
I’ve tried using the “Fix with V0 (Free)” option several times. I understand that these fixes no longer consume credits, but the problem is that when I try to redeploy and it fails again with the same error, credits are still being deducted from my account.
In short: the V0 fix itself is free, but the failed redeploy attempts still cost credits, even though the error isn’t resolved. This issue started today, without any relevant changes in my code.
Is anyone else experiencing the same problem? Has there been any recent change that explains why I can’t deploy something that worked fine yesterday?
Hey, @sergionvi! Welcome back to the Community It’s great to see you here again.
Looking at your build errors, it seems there are two separate issues to fix. I know you used v0 for this, but it would be helpful to also review your code against the following:
Lucide React Import Error
The Module not found error for lucide-react suggests the import path is incorrect. Make sure you’re importing icons like this:
import { PenSquare } from 'lucide-react'
Instead of trying to import from the dist path directly.
Server Actions Configuration
For the Server Actions error, you’ll need to enable the feature in your next.config.js:
“I’m getting build errors. First, the lucide-react import isn’t working. Please update the imports so they use import { IconName } from 'lucide-react'. Second, I need Server Actions enabled in Next.js, please update my next.config.js so that experimental.serverActions is set to true.”