👋 I'm Isidor, a PM from the VS Code team, and we recently announced VS Code for the Web at https://vscode.dev/, which provides a free, zero-install Microsoft Visual Studio Code experience running entirely in your browser. You can learn more here.
We'd like to ensure css-peak can run in the web, 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
I checked out your extension and this might be as simple as adding a browser property to your package.json that has the same value as the main property.
Would you be open for a PR that fixes this?
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!
👋 I'm Isidor, a PM from the VS Code team, and we recently announced VS Code for the Web at https://vscode.dev/, which provides a free, zero-install Microsoft Visual Studio Code experience running entirely in your browser. You can learn more here.
We'd like to ensure css-peak can run in the web, and we have a guide for enabling extensions for the web here. As a couple of highlights:
browserpropertyvscode.workspace.fsI checked out your extension and this might be as simple as adding a
browserproperty to yourpackage.jsonthat has the same value as themainproperty.Would you be open for a PR that fixes this?
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!