[Excalidraw Extension] Blank custom editor in Gitpod Browser IDE

[pomdtr]

Bug description

The excalidraw custom editor does not display properly in gitpod.

However, it works fine in github.dev, github codespaces and vscode.

Steps to reproduce

• Open the excalidraw-vscode repository in gitpod
• Install the excalidraw extension
• Open the examples/text.excalidraw file

Workspace affected

excalidraw-excalidrawvs-bs2w57wmia6.ws-eu47.gitpod.io

Expected behavior

On github.dev, the test.excalidraw file is shown:

Example repository

https://github.com/excalidraw/excalidraw-vscode

[filiptronicek]

Hi @pomdtr 👋, thanks for raising the issue. I can reproduce this and it seems like there is an error in the activation of the extension. I'll dig deeper, but this log is so far what I've got:

[2022-06-08 17:35:44.238] [exthost] [info] Extension host started
[2022-06-08 17:35:44.902] [exthost] [info] ExtensionService#_doActivateExtension pomdtr.excalidraw-editor, startup: true, activationEvent: 'workspaceContains:**/*.{excalidraw,excalidraw.svg,excalidraw.png}'
[2022-06-08 17:35:44.973] [exthost] [error] Activating extension pomdtr.excalidraw-editor failed due to an error:
[2022-06-08 17:35:45.016] [exthost] [error] Error: 
	at O._loadCommonJSModule (../../../vs/workbench/api/worker/extensionHostWorker.js:75:63362)
	at async Promise.all (index 0)
	at async f._activate (../../../vs/workbench/api/worker/extensionHostWorker.js:69:8180)
	at async f._waitForDepsThenActivate (../../../vs/workbench/api/worker/extensionHostWorker.js:69:8122)
	at async f._initialize (../../../vs/workbench/api/worker/extensionHostWorker.js:69:7486)

Source code of the error line: https://github.com/gitpod-io/openvscode-server/blob/d9373893583a1b78df346f4671bc24221d5e5aba/src/vs/workbench/api/common/extHostExtensionService.ts#L466

There is also a warning every time I open a file, which is https://github.com/microsoft/vscode/blob/05de94e4c547a8953d3c002fe034fa4589ebfa97/src/vs/workbench/api/common/extHostConfiguration.ts#L304.

[jeanp413]

I also took a look, it seems it's an openvsx bug, I created an issue upstream eclipse/openvsx#468