fix: enhance IPC error handling (#54)

Author: chenjiahan

src/rpc/expose-rpc.ts

@@ -1,7 +1,14 @@
-import process from 'process';
-
+import process from 'node:process';
 import type { RpcMessage } from './types';
 
+function isClosedIpcChannelError(error: unknown): boolean {
+  if (typeof error === 'object' && error !== null && 'code' in error) {
+    const CLOSED_IPC_ERROR_CODES = new Set(['ERR_IPC_CHANNEL_CLOSED', 'EPIPE']);
+    return CLOSED_IPC_ERROR_CODES.has(error.code as string);
+  }
+  return false;
+}
+
 // eslint-disable-next-line @typescript-eslint/no-explicit-any
 export function exposeRpc(fn: (...args: any[]) => any) {
   const sendMessage = (message: RpcMessage) =>
@@ -50,6 +57,13 @@ export function exposeRpc(fn: (...args: any[]) => any) {
           });
         }
       } catch (sendError) {
+        if (isClosedIpcChannelError(sendError)) {
+          console.warn(
+            '[type-check] Skipped because the parent process exited. Build may have failed or been interrupted.',
+          );
+          return;
+        }
+
         // we can't send things back to the parent process - let's use stdout to communicate error
         if (error) {
           console.error(error);