VSCode: allow `oxc.path.server` to be used in Linux & Windows

[Sysix]

I see #13542 was merged an hour ago. This only covers the case with the relative path, correct? I could not share oxc.path.server as a project wide setting in my .vscode/settings.json, if I have a mix of Windows and non-Windows developers as I sometimes would have to use .exe and sometimes not. (Referring to this comment.)

Originally posted by @donaldpipowitch in #12849

Created an own issue for it, because it is more work than expected.
There is no .exe, only .CMD and .ps1 (in NPM/PNPM).
Bun has .exe file in node_modules/.bin.

There could be 2 solutions:

Enable shell option, so VSCode can use node_modules/.bin/language_server too.
This will enable a security hole (#13732 (comment)), which should be covered by #13740 and #13734.
I would like to force somehow more checks before enabling this.

Search for .exe inside node_modules.
This could be a bit difficult because the package manager could but the file somewhere else than expected.
The other editors could have solved this already. But we should check if this works with different package managers as expected.

[nrayburn-tech]

The IntelliJ plugin allows users to specify either the location to the JavaScript file or the location to the exe. If the user doesn't provide a path, the default path is ${project_absolute_path}/node_modules/oxlint/bin/oxc_language_server.

We use an IntelliJ class for handling our command running, so I don't know what it might do after we provide it our info. https://github.com/oxc-project/oxc-intellij-plugin/blob/fd42b48af6add3e5ac6131578dfb59010a45515d/src/main/kotlin/com/github/oxc/project/oxcintellijplugin/OxcTargetRun.kt is where we build the IntelliJ class for executing commands.

I don't know what package managers/OS combinations the IntelliJ plugin has been tested with. I only really use NPM and primarily macOS.

[nrayburn-tech]

On macOS Bun, NPM, and PNPM creates the below.

• node_modules
  • .bin
    • oxc_language_server symlink to ../oxlint/bin/oxc_language_server
    • oxlint symlink to ../oxlint/bin/oxlint

With Bun and NPM, the files within .bin are just symlinks to the files within node_modules/oxlint/bin.

With PNPM, the files within .bin are sh files that change the NODE_PATH then execute the file within node_modules/oxlint/bin.

In each of those cases, I would expect to be able to execute the file located at node_modules/.bin/oxc_langauge_server in a cross platform way to run the actual language server executable without enabling shell: true. This adds a bit of overhead compared to running the exe directly, but it's likely worth it given the number of package managers at use and the different ways they may decide to store the actual exe file.

I think that users should be configuring the path to node_modules/.bin/oxc_language_server as their VS Code (or IntelliJ) setting. Even if users don't use that value exactly, they should be pointing to a file such as that which handles all of the underlying exe lookups and execution in a cross platform way. If users choose to do something else like configure the exe path directly, then it should still work but it is unlikely to work in a cross platform way and that's their responsibility.

---

All of my testing was on macOS, but I expect the same to hold true for Linux and Windows.