You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Call to Action: Please check whether your extension can handle virtual workspaces, and set the virtualWorkspaces capability accordingly in your package.json.
Marp extension is still using Node.js fs. It would be resolved by replacing to use VS Code workspace API.
The core problem is that slide export is depending on Marp CLI and it's using fs internally. It requires to change Marp CLI API, to accept alternative fs module.
Even so, exports depending on Puppeteer are not working because Chrome browser won't recognize files in VS Code virtual workspace. We may have to restrict export type to HTML export when the extension is working on a virtual workspace.
The text was updated successfully, but these errors were encountered:
https://code.visualstudio.com/updates/v1_56#_define-whether-your-extension-supports-a-virtual-workspace
For supporting virtual workspace
➡️ #225
Memo
Marp extension is still using Node.js
fs
.It would be resolved by replacing to use VS Code workspace API.The core problem is that slide export is depending on Marp CLI and it's usingfs
internally. It requires to change Marp CLI API, to accept alternativefs
module.Even so, exports depending on Puppeteer are not working because Chrome browser won't recognize files in VS Code virtual workspace. We may have to restrict export type to HTML export when the extension is working on a virtual workspace.
The text was updated successfully, but these errors were encountered: