Common Build Errors & Developer FAQ
Actionable solutions for exit code errors, package.json misconfigurations, memory thresholds, and general FAQs.
Diagnosing Common Build Errors
When a build fails, the Developer Terminal displays an actionable Failure Diagnostic Card. Here are solutions to the most frequent issues:
Solution: Verify your package.json contains a "build" script for frontend frameworks or a "start" script for Node.js backends.
Memory Limit Exceeded (Exit Code 137)
If your project fails with an Out-of-Memory (OOM) error during heavy compilation (e.g. large Next.js apps with many pages), optimize your build command with --max-old-space-size or upgrade to the Lite or Max tier with higher allocated container RAM.
Output Directory Not Found
If the build succeeds but deployment reports "Directory does not exist", verify the Output Directory setting matches your framework (e.g. "dist" for Vite, ".next" for Next.js, "build" for CRA).
Frequently Asked Questions
Can I host a database directly inside my AcadSites container?+
AcadSites containers are ephemeral and stateless. For persistent data, connect to managed cloud databases like Supabase, Neon, or MongoDB Atlas using environment variables.
How do I view raw build logs?+
Open your project, navigate to the Deployments tab, and click any deployment to inspect the full streaming terminal log. You can search, copy, or download the log.
Why does my custom domain show "Pending DNS"?+
DNS propagation can take between 2 and 15 minutes. Ensure your CNAME record points to cname.acadkits.dev and click "Verify DNS" after a few minutes.
Have a project ready to launch?
Join thousands of developers hosting on AcadSites with zero overage anxiety.