Update to [email protected] and [email protected]

[kaisalmen]

Changes:

• Update all dependencies:
  • [email protected]
  • [email protected]
  • Multiple others including [email protected]
• Removed dynamic imports:
  • initServices add both language and model service always and they are therefore a direct dependency of monaco-languageclient. Without them using this lib doesn't really make sense.
  • The examples package define the extra services and default-extensions the examples require in their dependencies

TODO:

• Update README
• Use final version of @codingame/monaco-vscode-api as soon as it released.

[kaisalmen]

@CGNonofr it is working nicely after I adapted the vite / experimental node config

[kaisalmen]

Next version is available: https://www.npmjs.com/package/monaco-languageclient/v/6.5.0-next.0

[CGNonofr]

@CGNonofr it is working nicely after I adapted the vite / experimental node config

Wonderful! Don't you want me to wait for the monaco-vscode-api final release before approving it?

[kaisalmen]

Wonderful! Don't you want me to wait for the monaco-vscode-api final release before approving it?

Yes, I also want/force-me to update the README on this branch. 🙂

[kaisalmen]

@CGNonofr updated to 1.82.2
Next version is available: https://www.npmjs.com/package/monaco-languageclient/v/6.5.0-next.1

The README is basically ready. Should we remove the monaco-editor-core section from the troubleshooting section. This no longer relevant. WDYT?

[kaisalmen]

@CGNonofr this is now ready to be merged. Further README clarification don't block this, I think.

[kaisalmen]

@CGNonofr I have not released a final version, because I discovered a nasty problem in monaco-editor-wrapper and here is the solution:
https://github.com/TypeFox/monaco-components/blob/next-mlc/packages/examples/src/langium/config/wrapperLangiumVscode.ts#L42-L43
https://github.com/TypeFox/monaco-components/blob/next-mlc/packages/monaco-editor-wrapper/src/editorAppBase.ts#L212-L221
When you load an extension for a language (Langium Web Worker LS) you now have to await the loading of the theme before you load the language extension. Otherwise the theme does not work. This behaviour changed with [email protected]. It was no problem before. Are you aware of this change in behaviour?

[kaisalmen]

@CGNonofr the problem is that sometimes the loading of extensions (e.g. themes) happens before and sometimes after. It seems that something that has been awaited before (1.81.x) and now not (1.82.x). Maybe something needs to be adjusted in monaco-vscpde-api. I haven't looked into the code. It is anyway good I have the other mechanism above in place.