monaco-vscode-api: Services with 1.86.6 version produce error

When i update from 1.86.5 to 1.86.6 the error appear (langauge client also 7.0.1):

t Module.ok (assert.js:22:1)
    at RegistryImpl.add (platform.js:14:1)
    at eval (editor.js:317:1)
    at ./node_modules/.pnpm/@codingame+monaco-vscode-api@1.83.5/node_modules/@codingame/monaco-vscode-api/vscode/src/vs/workbench/common/editor.js (vendors-node_modules_pnpm_codingame_monaco-vscode-api_1_83_5_node_modules_codingame_monaco-vs-b6ede8.js:92:1)
    at __webpack_require__ (runtime.js:31:42)
    at eval (editorGroupsService.js:15:75)
    at ./node_modules/.pnpm/@codingame+monaco-vscode-api@1.83.5/node_modules/@codingame/monaco-vscode-api/vscode/src/vs/workbench/services/editor/common/editorGroupsService.js (vendors-node_modules_pnpm_codingame_monaco-vscode-api_1_83_5_node_modules_codingame_monaco-vs-b6ede8.js:197:1)
    at __webpack_require__ (runtime.js:31:42)
    at eval (editorService.js:9:81)
    at ./node_modules/.pnpm/@codingame+monaco-vscode-api@1.83.5/node_modules/@codingame/monaco-vscode-api/vscode/src/vs/workbench/services/editor/common/editorService.js (vendors-node_modules_pnpm_codingame_monaco-vscode-api_1_83_5_node_modules_codingame_monaco-vs-b6ede8.js:204:1)

About this issue

  • Original URL
  • State: closed
  • Created 8 months ago
  • Comments: 15 (4 by maintainers)

Most upvoted comments

@CGNonofr thank you. Still recovering. Will continue to support this if I can keep up with the changes you and @CompuIves put out. šŸ‘€ šŸ’Ŗ Regarding monaco-languageclient everything evolved the right way. No regrets there.

Very heartwarming message!

I’m probably the most active dev here, but it would be really unfair to not mention @kaisalmen who has provided a lot of support (and I hope will continue to) and who has seen their library monaco-languageclient depleted of its essence slowy as this lib became more VSCode compliant

You have to add "vscode": "npm:@codingame/monaco-vscode-api@>=1.83.7 <1.84.0", to your overrides, then this should force everything depending on it to be in-line. If that is not sufficient, then add more overrides. I will release a new monaco-languageclient version today or tomorrow as well.

probably a version mismatch somewhere

@BusinessDuck yes, I just had a problem two hours ago where the monaco-editor override with @codingame/monaco-editor-treemended was not correct. npm list is your friend in such cases. Removing package-lock.json and deleting node_modules and re-installing everything once you are certain all dependencies/overrides/resolutions are correct helps.