Our monolithic Nuxt app kept crashing at the 2GB memory limit. We doubled to 4GB — twice the cost, same underlying problem. After five days of failed optimization attempts (streaming compression, Redis polling, SWR caching), we split the monolith into three standalone services. Each got its own 2GB allocation, total cost dropped, and the crashes stopped.
We added Arabic and Portuguese to our Nuxt i18n setup but blocked them from production. The problem? Sitemaps, hreflang tags, and crawlers didn't get the memo — generating thousands of wasted URLs, doubling API calls, and burning through serverless invocations.
While optimizing a Nuxt 3 project, I discovered excessive automatic prefetching was driving up Vercel bandwidth. Disabling prefetch globally brought costs and network overhead way down.
I inherited a Nuxt 3 project that was costing over $50/day in Vercel bandwidth. The culprit? A single wildcard import pulling in the entire Font Awesome library. Here’s how I found and fixed it.
Git worktrees are amazing for parallel development, but Vercel CLI breaks in them. Here is the fix for Nuxt monorepo projects.
With these adjustments, my application ran smoothly on Vercel. Finally, I could get some well-deserved rest! 🎉