Don't immediately exit on Pages Functions compilation error (#671)

* Don't immediately exit on Pages Functions compilation error

* Update .changeset/tame-timers-brake.md

Co-authored-by: Pete Bacon Darwin <pete@bacondarwin.com>

Co-authored-by: Pete Bacon Darwin <pete@bacondarwin.com>

.changeset/tame-timers-brake.md

@@ -0,0 +1,7 @@
+---
+"wrangler": patch
+---
+
+fix: don't exit on initial Pages Functions compilation failure
+
+Previously, we'd exit the `wrangler pages dev` process if we couldn't immediately compile a Worker from the `functions` directory. We now log the error, but don't exit the process. This means that proxy processes can be cleaned up cleanly on SIGINT and SIGTERM, and it matches the behavior of if a compilation error is introduced once already running (we don't exit then either).

packages/wrangler/src/pages.tsx

@@ -805,13 +805,15 @@ export const pages: BuilderCallback<unknown, unknown> = (yargs) => {
 
           console.log(`Compiling worker to "${scriptPath}"...`);
 
-          await buildFunctions({
-            scriptPath,
-            functionsDirectory,
-            sourcemap: true,
-            watch: true,
-            onEnd: () => scriptReadyResolve(),
-          });
+          try {
+            await buildFunctions({
+              scriptPath,
+              functionsDirectory,
+              sourcemap: true,
+              watch: true,
+              onEnd: () => scriptReadyResolve(),
+            });
+          } catch {}
 
           watch([functionsDirectory], {
             persistent: true,