feat(nitro-node): trap terminate signal in order to kill nitro process

As nitro process is spawned in daemon mode, the library should be
able to trap SIGTERM signal in order to kill nitro process.

Author: InNoobWeTrust

nitro-node/src/nitro.ts

@@ -152,7 +152,9 @@ export async function checkMagicBytes(
     chunks.push(chunk);
   }
   const actual = Buffer.concat(chunks);
-  log(`Comparing file's magic bytes <${actual.toString()}> and desired <${desired.toString()}>`);
+  log(
+    `Comparing file's magic bytes <${actual.toString()}> and desired <${desired.toString()}>`,
+  );
   return Buffer.compare(actual, desired) === 0;
 }
 
@@ -499,3 +501,11 @@ export async function getResourcesInfo(): Promise<ResourcesInfo> {
 export const updateNvidiaInfo = async () =>
   await _updateNvidiaInfo(nvidiaConfig);
 export const getCurrentNitroProcessInfo = () => getNitroProcessInfo(subprocess);
+
+/**
+ * Trap for system signal so we can stop nitro process on exit
+ */
+process.on("SIGTERM", async () => {
+  log(`[NITRO]::Debug: Received SIGTERM signal`);
+  await killSubprocess();
+});

nitro-node/src/scripts/download-nitro.ts

@@ -150,7 +150,7 @@ const downloadBinaries = (
   );
 };
 
-// Check for a files with nitro in name in the corresponding directory
+// Check for files with nitro in name in the corresponding directory
 const verifyDownloadedBinaries = (absBinDirPath: string) => {
   // Check all the paths in variantConfig for a file with nitro in its name
   return Object.values(variantConfig).every((binDirVariant: string) => {