Cucumber fails to start in VSCode with Cucumber Language Server client: couldn't create connection to server error

[jm-paulin]

👓 What did you see?

upon starting VSCode, when we access a feature file for the first time we see in the output:

[Error - 1:32:37 PM] Server initialization failed.
  Message: Request initialize failed with message: bad export type for `tree_sitter_c_sharp_external_scanner_create`: undefined
  Code: -32603 
[Error - 1:32:37 PM] Cucumber Language Server client: couldn't create connection to server.
  Message: Request initialize failed with message: bad export type for `tree_sitter_c_sharp_external_scanner_create`: undefined
  Code: -32603 

Feature files are not highlighted, no hyperlink works.

✅ What did you expect to see?

No error in the putput windows, features file to have syntax highlithing

📦 Which tool/library version are you using?

VSCode:

Version: 1.90.1 (user setup)
Commit: 611f9bfce64f25108829dd295f54a6894e87339d
Date: 2024-06-11T21:01:24.262Z
Electron: 29.4.0
ElectronBuildId: 9593362
Chromium: 122.0.6261.156
Node.js: 20.9.0
V8: 12.2.281.27-electron.0
OS: Windows_NT x64 10.0.22631

and plugins

$ code --list-extensions --show-versions
cucumberopen.cucumber-official@1.10.0
foxundermoon.shell-format@7.2.5
golang.go@0.41.4
josevseb.google-java-format-for-vs-code@1.1.2
ms-azuretools.vscode-docker@1.29.1
ms-python.debugpy@2024.6.0
ms-python.python@2024.8.1
ms-python.vscode-pylance@2024.6.1
possan.nbsp-vscode@0.0.1
redhat.fabric8-analytics@0.9.4
redhat.java@1.31.0
redhat.vscode-xml@0.27.1
redhat.vscode-yaml@1.15.0
visualstudioexptteam.intellicode-api-usage-examples@0.2.8
visualstudioexptteam.vscodeintellicode@1.3.1
vscjava.vscode-java-debug@0.57.0
vscjava.vscode-java-dependency@0.23.6
vscjava.vscode-java-pack@0.27.0
vscjava.vscode-java-test@0.41.1
vscjava.vscode-maven@0.44.0

Running in Ubuntu/WSL2 susbsystem

🔬 How could we reproduce it?

Looks like I am not the only one to see this. https://github.com/cucumber/vscode/issues/155#issuecomment-2178719719

📚 Any additional context?

Started about a week ago. could well be related to a VSCode version update.

[jm-paulin]

Closing as this is a duplicate of #234