💩 [Debug] Get details about segmentation faults using the `segfault-h…

…andler` package

package.json

@@ -40,6 +40,7 @@
     "command-join": "^3.0.0",
     "cross-spawn": "^7.0.2",
     "mri": "^1.2.0",
+    "segfault-handler": "1.3.0",
     "which-pm": "^2.0.0",
     "which-pm-runs": "^1.1.0"
   },

src/utils/config.ts

@@ -1,3 +1,8 @@
+// ///// ↓DEBUG↓ /////
+import path from 'node:path';
+import url from 'node:url';
+
+// ///// ↑DEBUG↑ /////
 import { execFileAsync, isObject } from '../utils.js';
 import { getPackageManagerData } from './detect-package-manager.js';
 
@@ -22,6 +27,14 @@ async function tryNpmConfigGet(key: string): Promise<string | null> {
             // This allows npm commands to be used even in projects with non-npm package managers defined.
             // see https://github.com/nodejs/corepack/tree/v0.14.0#environment-variables
             COREPACK_ENABLE_STRICT: '0',
+            // ///// ↓DEBUG↓ /////
+            NODE_OPTIONS:
+                `${process.env['NODE_OPTIONS'] ?? ''} ` +
+                `--require "${path.resolve(
+                    url.fileURLToPath(import.meta.url),
+                    '../segfault-handler.cjs',
+                )}"`,
+            // ///// ↑DEBUG↑ /////
         },
     })
         .then(({ stdout }) => stdout.replace(/\n$/, ''))

src/utils/segfault-handler.cts

@@ -0,0 +1,4 @@
+import path from 'path';
+import SegfaultHandler from 'segfault-handler';
+
+SegfaultHandler.registerHandler(path.join(process.cwd(), 'crash.log'));