@creatorem/cli 1.0.4 → 1.0.5

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@creatorem/cli",
-  "version": "1.0.4",
+  "version": "1.0.5",
   "description": "CLI tool for Creatorem SaaS Kit",
   "author": "Creatorem",
   "license": "MIT",

package/src/shims/signal-exit.js

@@ -1,9 +1,32 @@
-// Bypass the alias by importing from the specific file in node_modules
-// We use a relative path that we hope resolves correctly from dist/
-// But since we are bundling, we need the path relative to THIS file (src/shims/signal-exit.js)
-// AND we need to make sure esbuild doesn't treat it as the aliased package.
-// Using a relative path to node_modules/signal-exit/dist/mjs/index.js usually works.
-import { onExit, load, unload } from '../../node_modules/signal-exit/dist/mjs/index.js';
+import { createRequire } from 'module';
+
+const require = createRequire(import.meta.url);
+
+function resolveSignalExitModule() {
+    // Try direct package first, then common nested locations used by pnpm trees.
+    const candidates = [
+        'signal-exit',
+        'execa/node_modules/signal-exit',
+        'foreground-child/node_modules/signal-exit',
+    ];
+
+    for (const modId of candidates) {
+        try {
+            return require(modId);
+        } catch {
+            // try next candidate
+        }
+    }
+
+    throw new Error('Could not resolve signal-exit from known locations');
+}
+
+const signalExit = resolveSignalExitModule();
+
+// v4 exports named onExit/load/unload. v3 exports a function with load/unload props.
+const onExit = signalExit.onExit ?? signalExit.default ?? signalExit;
+const load = signalExit.load ?? (() => {});
+const unload = signalExit.unload ?? (() => {});
 
 export default onExit;
 export { onExit, load, unload };