monaco-languageclient: issue with v6.5.0 (There is already an extension with this id error) on inputFactories

@kaisalmen might this be something for the troubleshooting section? this is including mine the 3rd occurrance of this problem? (see also https://github.com/TypeFox/monaco-languageclient/issues/538)

@cdietrich Worked like a charm, thank you 🥳

New release is available: https://www.npmjs.com/package/monaco-languageclient/v/6.5.1

Thank you all for getting to the bottom of this fairly quickly!

@CGNonofr Ok, so whatever we have it is not compatible with regular monaco-editor tooling in the end or needs proper customization (see https://github.com/CodinGame/monaco-vscode-api/issues/219). Wouldn’t it then make sense to fully rely/rename (also for all your packages) on a self-standing npm package e.g. called monaco-vscode-api-editor that can be used in combination with overrides / resolutions to override monaco-editor. It is basically what is done here already.

This way people realize the have something else and could force it in the dependency chain instead of monaco-editor. Also, then people no longer need such tooling (MonacoWebpackPlugin), right? Does it make sense? WDYT?

i had to resolve buffer to a newer version in package.json

"resolutions": {
   ...
    "buffer": "^6.0.3",
    ...
  }

the vscode buffer checks if buffer is available in global and if yes uses that one

@kaisalmen according to chatGPT 😭

"vscode": "npm:@codingame/monaco-vscode-api@>=1.82.0 <1.83.0"

I added it to my package.json

I can confirm the vscode version mismatch in monaco-languageclient@6.5.0