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
I have seen other issues related like: #22, but this is still not solved, because it also happens with web extensions on places like github.dev.
If your extension uses workspace.fs to open a file, and launch vscode-test-web with a folder to open, or use (.) on a github repository, while vscode will load properly and will open the folder correctly, your extension won't be able to use workspace.fs to load files by itself.
On the other hand, if you just open VSCode.dev and open the folder you want, then, your extension will work properly. I cannot understand why such a different behavior.
The text was updated successfully, but these errors were encountered:
That message ENOPRO: No file system provider found for resource 'vscode-test-web://mount/' appears at the beginning but doesn't mean much.
The sample and tests in test-web accesses the vscode-test-web://mount/ file system, so this should work
run npm run sample to open the sample extension in vs code web.
I have seen other issues related like: #22, but this is still not solved, because it also happens with web extensions on places like github.dev.
If your extension uses workspace.fs to open a file, and launch vscode-test-web with a folder to open, or use (.) on a github repository, while vscode will load properly and will open the folder correctly, your extension won't be able to use workspace.fs to load files by itself.
On the other hand, if you just open VSCode.dev and open the folder you want, then, your extension will work properly. I cannot understand why such a different behavior.
The text was updated successfully, but these errors were encountered: