fix: correct shebang regex

We were incorrectly looking for the end of the input, which meant most
shebangs were not being matched 👀

Author: 43081j

src/normalize.ts

@@ -11,7 +11,7 @@ import {getPathFromEnv} from './env.js';
 
 // See http://www.robvanderwoude.com/escapechars.php
 const metaCharsRegExp = /([()\][%!^"`<>&|;, *?])/g;
-const shebangRegExp = /^#!\s*(.+)$/;
+const shebangRegExp = /^#!\s*(.+)/;
 const isWindowsExecutableRegExp = /\.(?:com|exe)$/i;
 const isNodeModulesCmdRegExp = /node_modules[\\/]\.bin[\\/][^\\/]+\.cmd$/i;
 const isWindows = process.platform === 'win32';

src/test/normalize_test.ts

@@ -61,6 +61,16 @@ describe('normalizeSpawnCommand', () => {
       });
     });
 
+    test('detects shebang and rewrites command to interpreter', () => {
+      const scriptPath = path.join(fixturesPath, 'shebang_script.js');
+      const normalized = normalizeSpawnCommand(scriptPath, []);
+
+      // where resolves to where.exe (always a .exe in System32, never a
+      // shim), so the cmd.exe wrapping branch is skipped
+      expect(normalized.command).toBe('where');
+      expect(normalized.args).toEqual([scriptPath]);
+    });
+
     test('handles relative commands without extension', () => {
       const relativePath = path.relative(
         cwd,

test/fixtures/shebang_script.js

@@ -0,0 +1,2 @@
+#!where
+not a real script, just used to verify shebang parsing