Support VS Code for the Web

[AndreaPi]

Proposal

Visual Studio Code for the Web is the web-based editor that powers github.dev.

Being compatible with it can help the Markdown editing experience on GitHub in web browser.

References

• The github.dev web-based editor | GitHub Docs

• Why is an extension not installable in the browser

• Web Extensions authoring guide

[yzhang-gh]

I've enabled the virtual workspaces support although some features may not work as expected.

People who are interested can install the dev build.
https://code.visualstudio.com/api/advanced-topics/remote-extensions#installing-a-development-version-of-your-extension

[Lemmingh]

Too many modules depend on sync fs, while VS Code's fs is async. That's the major problem.

[Lemmingh]

According to a recently published authoring guide, there is much more to do than just supporting Virtual Workspaces.

[isidorn]

Hi, VS Code PM here 👋

Yeah, we would love to have vscode-markdown available on the web if that is possible.
And we have a guide for enabling extensions for the web here. As a couple of highlights:

• In VS Code for the Web, both the UI and extension host run inside the browser.
• A web extension is structured like a regular extension, but with a different main file: it's defined by the browser property
• Access to workspace files needs to go through the VS Code file system API accessible at vscode.workspace.fs
• There are currently three ways to test a web extension

@yzhang-gh Please let us know if you have questions or feedback on enabling your extension for the web - our team would love to learn from your experiences and collaborate. Thank you!

[yzhang-gh]

Thanks for reaching out.

I am willing to make this extension available for the VS Code Web. However, I won't have enough time to do this until (exactly) one month later...

[isidorn]

This is great news. In a couple of months would be great!

[0x-jerry]

I have published a fork of this extension that supports vscode web with some limitations. markdown-all-in-one-for-web

Limitations:

• No NLS, only English.
• No print to pdf.
• No welcome message.

I wish this could help you.

Because of the limitations, it can not merge directly, so I am not making a PR. Also, I am not fully testing the change I made.

Btw, Thank you made this great extension. @yzhang-gh

[isidorn]

@0x-jerry thanks for working on this. Instead of publishing a fork can you instead open a PR to this extension. I think that would be more helpful? Thanks a lot!

[0x-jerry]

@isidorn Yes, I agree with you. But as I mentioned above, there have some limitations that need to be solved. And it needs time to solve that which I don't have recently. That is why I am not open a PR, I will try to solve those limitations and open a PR when I have time, but that may take a long time.

[Lemmingh]

Prerequisites:

• Build system: Publish Pre-Release automatically #1054

• NLS: Move UI localization resources into code #1025

• POSIX path utilities: https://github.com/nodejs/node/blob/master/lib/path.js

• Base64 Encoding API: https://github.com/nodejs/node/blob/master/src/base64-inl.h

[tuta-amb]

Is this still being worked on?

[yzhang-gh]

Unfortunately no as it requires a relative long period of time to sort all these things out.