Loïc Mangeonjean

As the compatibility table states, [email protected] should not be used with v9 of monaco-vscode-api (and all other @codingame packages) also, you don't need `monaco-editor`

btw @kaisalmen, having `monaco-editor` in the compatibility table is quite confusing, it's only for informative purpose and we should probably say that it shouldn't be installed

Btw, it works on https://monaco-vscode-api.netlify.app/, which also uses the typescript default extension > Perhaps they are using the [@codingame/monaco-vscode-standalone-typescript-language-features service](https://www.npmjs.com/package/@codingame/monaco-vscode-standalone-typescript-language-features) to accomplish this? Yes we are, but just because enabling...

Actually, it's because of those options: ```json "typescript.tsserver.experimental.enableProjectDiagnostics": true, "typescript.tsserver.web.projectWideIntellisense.suppressSemanticErrors": false, ```

Or maybe not 🤔

I can probably a minimal repo exemple, but the suggested fix seems obvious enough to me to understand the issue that was already fixed somewhere else in the code in...

I've attached a PR to the issue, why are you closing it ??

Is the reproduction repo still required? Is there anything I can do to help moving forward on this?

I was actually able to add a shadow dom test, see the attached PR

Those open-source libraries are only maintained by 2 persons not working on it full-time. There is room for improvements. We are talking about integrating IDE-like features in one's app, with...