do not process exit under jest

TODO.md

@@ -4,10 +4,11 @@
 
 - [ ] #now redo logging to use the debug module
 - [ ] support node v20
+  - See https://github.com/sagemathinc/websocketfs/issues/1 
+  - May be entirely an issue for unit testing.
 
 # DONE
 
-
 - [x] there are a bunch of TODO's in the code still -- read them; delete ones that aren't relevant or address, or leave ones that may matter later.  Result: most of the worrisome ones are in copy functions that FUSE doesn't use.
 - [x] Remove all auth (was: support auth, i.e., an optional symmetric key that clients must present to be allowed to mount the filesystem. This is useful for "defense in depth".). It's better to do the auth at a different level.
 - [x] delete the "WEB" comments in code...

lib/fuse/bind.ts

@@ -13,7 +13,9 @@ export default async function bind(source: string, target: string) {
   const exitHandler = async () => {
     server.end();
     await unmount();
-    process.exit();
+    if (process.env.JEST_WORKER_ID == null) {
+      process.exit();
+    }
   };
 
   process.on("exit", exitHandler);
@@ -24,7 +26,6 @@ export default async function bind(source: string, target: string) {
     unmount: async () => {
       server.end();
       await unmount();
-      process.exit();
     },
     fuse,
     server,