fix: improve resource_exhausted error message (#3020)

Author: deepshekhardas

packages/core/src/v3/errors.test.ts

@@ -0,0 +1,22 @@
+import { describe, it, expect } from "vitest";
+import { prepareDeploymentError } from "./errors.js";
+
+describe("prepareDeploymentError", () => {
+    it("should handle [resource_exhausted] error with a friendly message", () => {
+        const errorData = {
+            name: "Error",
+            message: "Build failed: [resource_exhausted] Process exited with code 1",
+            stderr: "Some stderr output",
+        };
+
+        const result = prepareDeploymentError(errorData);
+
+        // Initial expectation: it passes through (before fix)
+        // After fix: it should have a specific message about build resources.
+        // For now, let's just assert it returns SOMETHING.
+        expect(result).toBeDefined();
+        expect(result!.name).toBe("BuildError");
+        expect(result!.message).toContain("The build failed because it ran out of resources");
+        expect(result!.message).toContain("Try reducing the size of your build context");
+    });
+});

packages/core/src/v3/errors.ts

@@ -1023,6 +1023,19 @@ export function prepareDeploymentError(
     }
   }
 
+  if (
+    errorData.message.includes("resource_exhausted") ||
+    errorData.stderr?.includes("resource_exhausted")
+  ) {
+    return {
+      name: "BuildError",
+      message:
+        "The build failed because it ran out of resources (memory or disk space). This can happen if you have a large build context or are installing heavy dependencies. Try reducing the size of your build context (use .dockerignore) or contact support if this persists.",
+      stderr: errorData.stderr,
+      stack: errorData.stack,
+    };
+  }
+
   return {
     name: errorData.name,
     message: errorData.message,