Extension activation fails on Visual Studio Code for the Web

[paulovmr]

Describe the bug

The extension activation fails on Visual Studio Code for the Web with Linux. With the following error in the browser Developer Tools console: Activating extension 'redhat.vscode-yaml' failed: Cannot access 'l' before initialization.. Same issue could not be observed on macOS.

Expected Behavior

Extension should initialize successfully.

Current Behavior

Extension fails to initialize and error in the description can be seen in the developer tools console.

Steps to Reproduce

1. Go to https://vscode.dev/
2. Install the YAML extension
3. Create a new *.yaml file

Environment

• [ ] Windows
• [ ] Mac
• [x] Linux
• [ ] other (please specify)

[brian-mulier-p]

Hello ! Any news on this issue ? Seems like a fix was merged but I still get the issue when trying to run an extension that depends on YAML extension latest (v1.14.0).

When is the next extension release planned ? Unfortunately it is a blocker on my side :cry:

Thank you ! :+1:

[pimguilherme]

hi guys! a quick workaround here is setting the default user agent to something different than linux:

it's not ideal but it's a quick setting (note that you must have this setting set up and the reload the page.. and then you can close the inspector, but it you load the page again it's likely to bug back)

[pimguilherme]

note that this must be done in some way that the window.navigator.userAgent setting is changed.. this does not occur with a UA swtich extension.. this way does..

you could probably also change this at launch time with some launch opt

[brian-mulier-p]

Hey ! Thanks for the tip ! It works but I'm integrating vscode onto a website and I don't want each of our users to do this fix :cry: Sorry for bothering but up again, when is the next release planned ?

[brian-mulier-p]

FYI I ended up creating a fork to bump the dep while a release is done :+1:

[pimguilherme]

oh that's nice @brian-mulier-p ! thanks :D

I didn't quite grasp the whole concept.. are you somehow embedding the extension in your VSCode web installtion in kestra without having to load it from the marketplace?

In my case, we are developing a VSCode plugin which depends on this one.. it doesn't sound very straightforward to bundle it together with this custom plugin (like perhaps activating both extensions through a common entry point)

[brian-mulier-p]

Sorry late response but yes we have to do it this way while the new version including the bugfix is released. I think if you load the dependency already built before it won't load it from marketplace :+1:

[hlshen]

Experiencing the same issue. Bundling our extension that depends on vscode-yaml with a code-oss installation.