That's true, want to work on a PR? should be pretty straightforward:

Thanks for asking, I might. Will post here if I pick this up. 💟

I have faced the weirdest issue that might be related. I was using a Windows machine and in a Next.js project of mine I have Jest 29.7 configured manually, exactly as depicted in this article. If there was any key difference from a typical Next.js project, it is that I was using pnpm. I took care to set jestCommandLine to pnpm run test -- (package.json/scripts/test was set to "jest" of course) but if I did that, the command line built upon running from the extension is like

jest "--" "--testLocationInResults" "--json" "--useStderr" ...

and then Jest wouldnt find any of my tests and exit with error (testRegex would get 0 matches). I found out that the "--" in jest invocation was causing all this, what I did not expect was that setting jestCommandLine to pnpm test -- would fix this issue. It makes no sense, but then maybe this was the cause.

{
    "configurations": [
        {
            "type": "node",
            "name": "vscode-jest-tests.v2..leetcode",
            "request": "launch",
            "args": [
                "--runInBand",
                "--watchAll=false",
                "--testNamePattern",
                "${jest.testNamePattern}",
                "--runTestsByPath",
                "${jest.testFile}"
            ],
            "cwd": "/Users/bubu/.leetcode",
            "console": "integratedTerminal",
            "internalConsoleOptions": "neverOpen",
            "disableOptimisticBPs": true,
            "program": "[project root]/node_modules/.bin/jest" // PNPM REWRITES IT TO SHELL BY DEFAULT
        }
    ]
}

However , the core problem is that pnpm creates the Jest binary file (node_modules/.bin/jest) as a shell script rather than a Node.js script, which cause issue like #868 . and this is also why #1046 would not work.

basedir=$(dirname "$(echo "$0" | sed -e 's,\\,/,g')")
          ^^^^^^^

SyntaxError: missing ) after argument list
    at Object.compileFunction (node:vm:352:18)
    at wrapSafe (node:internal/modules/cjs/loader:1033:15)
    at Module._compile (node:internal/modules/cjs/loader:1069:27)
    at Module._extensions..js (node:internal/modules/cjs/loader:1159:10)
    at Module.load (node:internal/modules/cjs/loader:981:32)
    at Module._load (node:internal/modules/cjs/loader:827:12)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12)
    at node:internal/main/run_main_module:17:47

User's own jestCommandLine might also not be node js as well, so the program field is not the answer. (scripts in package.json could also be shell scripts)
The alternatives' are

1. make runtimeExecutable in package.json sh (But this probably would not work on windows, we need find out how to work on window)
2. make runtimeExecutable pnpm
   Pnpm do have settings like prefer-symlinked-executables, but it is not default and might not be used on windows.
   so it would be nice to make this plugin support pnpm and other future package managers.
   @connectdotz