linter: Bun can't run Oxlint with `--type-aware` on Windows: Failed to find tsgolint executable

[Dimava]

What version of Oxlint are you using?

latest

What command did you run?

bun oxlint --type-aware

What does your .oxlintrc.json config file look like?

I'm not using a config file

What happened?

mkdir repro
cd repro
bun init -y
git init && echo "(otherwise oxlint lints node_modules)"
bun i -D bun i -D oxlint oxlint-tsgolint
dir node_modules\.bin
bun oxlint --type-aware

Output:

 Directory of repro\node_modules\.bin

15/09/2025  17:20    <DIR>          .
15/09/2025  17:20    <DIR>          ..
15/09/2025  17:20                36 bun.bunx
15/09/2025  17:20            13,824 bun.exe
15/09/2025  17:20                38 bunx.bunx
15/09/2025  17:20            13,824 bunx.exe
15/09/2025  17:20                84 oxc_language_server.bunx
15/09/2025  17:20            13,824 oxc_language_server.exe
15/09/2025  17:20                58 oxlint.bunx
15/09/2025  17:20            13,824 oxlint.exe
15/09/2025  17:20                60 tsc.bunx
15/09/2025  17:20            13,824 tsc.exe
15/09/2025  17:20                86 tsgolint.bunx
15/09/2025  17:20            13,824 tsgolint.exe
15/09/2025  17:20                70 tsserver.bunx
15/09/2025  17:20            13,824 tsserver.exe
              14 File(s)         97,200 bytes
               2 Dir(s)  22,811,107,328 bytes free

Failed to find tsgolint executable

[camc314]

@Sysix any ideas? should we be looking for a .exe maybe rather than a .CMD?

oxc/crates/oxc_linter/src/tsgolint.rs

Line 766 in 8f37e88

let file = if cfg!(windows) { "tsgolint.CMD" } else { "tsgolint" };

[camchenry]

@camc314 I think we need to consider all the variables in PATHEXT: https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_environment_variables?view=powershell-7.5

The $Env:PATHEXT variable contains a list of file extensions that Windows considers to be executable files.

That list seems to be: .COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.WSF;.WSH. I'm guessing that we could probably simplify things and just support .EXE, .BAT, and .CMD?

[camc314]

hmm this works with npm and pnpm. pnpm produces the following in .bin. I don't know why bun does something different

Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
-a---           9/15/2025  3:03 PM           1882 napi
-a---           9/15/2025  3:03 PM           1572 napi-raw
-a---           9/15/2025  3:03 PM           1264 napi-raw.CMD
-a---           9/15/2025  3:03 PM           2283 napi-raw.ps1
-a---           9/15/2025  3:03 PM           1546 napi.CMD
-a---           9/15/2025  3:03 PM           2587 napi.ps1
-a---           9/15/2025  3:03 PM           1384 oxc_language_server
-a---           9/15/2025  3:03 PM           1076 oxc_language_server.CMD
-a---           9/15/2025  3:03 PM           2065 oxc_language_server.ps1
-a---           9/15/2025  3:03 PM           1358 oxlint
-a---           9/15/2025  3:03 PM           1050 oxlint.CMD
-a---           9/15/2025  3:03 PM           2013 oxlint.ps1
-a---           9/15/2025  3:03 PM           1224 tsc
-a---           9/15/2025  3:03 PM            916 tsc.CMD
-a---           9/15/2025  3:03 PM           1843 tsc.ps1
-a---           9/15/2025  3:03 PM           1310 tsgolint
-a---           9/15/2025  3:03 PM           1002 tsgolint.CMD
-a---           9/15/2025  3:03 PM           1965 tsgolint.ps1
-a---           9/15/2025  3:03 PM           1234 tsserver
-a---           9/15/2025  3:03 PM            926 tsserver.CMD
-a---           9/15/2025  3:03 PM           1863 tsserver.ps1
-a---           9/15/2025  3:03 PM           1270 vitest
-a---           9/15/2025  3:03 PM            990 vitest.CMD
-a---           9/15/2025  3:03 PM           1989 vitest.ps1

According to the npm docs

To use this, supply a bin field in your package.json which is a map of command name to local file name. When this package is installed globally, that file will be either linked inside the global bins directory or a cmd (Windows Command File) will be created which executes the specified file in the bin field, so it is available to run by name or name.cmd (on Windows PowerShell). When this package is installed as a dependency in another package, the file will be linked where it will be available to that package either directly by npm exec or by name in other scripts when invoking them via npm run.

We're looking for .cmd. I don't know why bun doesn't call it that.

It might be a bug in bun? It feels silly to have to check every one of those extensions, when npm says it should be called a .cmd file.

Let me think about it

[Sysix]

I guess the .cmd and .ps1 files are generated by NPM itself as a wrapper for the native binary.
They will resolve to the native binary (.exe, or shell) depending on the platform/arch.

Do not know exactly what bun does, but looks like it will auto resolve it instead of creating a wrapper script. 🤔
I'm OK with searching .CMD for (P)NPM and .exe for other dependency managers

[Dimava]

Seems like all other PMs (npm, pnpm, yarn) use .CMD

We're looking for .cmd. I don't know why bun doesn't call it that.

Because it make EXEs /shrug
Noone else makes an EXE
Even deno makes CMD

@REM node_modules\.bin\oxlint.cmd
@deno run -A npm:oxlint@1.16.0/oxlint %*

[Dimava]

why bun doesn't call it that

CMD is a shell file
EXE is a binary (like what you get when compiling C)

[Boshen]

Seems like a Bun problem? Shall we close as not planned?

[Sysix]

Shall we close as not planned?

I am not sure if bun will fix this, see oven-sh/bun#22735 (comment)
On Linux/macOS with bun is working?

We could extend the search for windows. CMD → EXE → Throw Error

[Dimava]

Just in case checked if repro works in Linux docker container, np problems

Seems like a Bun problem? Shall we close as not planned?

It's not a bug, it's a feature (I made an issue on Bun repo to make sure it's searchable there)

The combination of .exe + .bunx files replace .cmd, .sh, .ps1 and the other wrappers. You can learn more about this in the Bun v1.1 release notes, which we will add as separate documentation since we appear to not have documented this elsewhere yet.

So I think it should be supported