Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ENOPRO: No file system provider found for resource 'vscode-test-web://mount/' #109

Open
qadram opened this issue Oct 25, 2023 · 1 comment

Comments

@qadram
Copy link

qadram commented Oct 25, 2023

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.

@aeschli
Copy link
Contributor

aeschli commented Oct 27, 2023

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.

Can you show the problem by making changes to https://github.com/microsoft/vscode-test-web/tree/main/sample ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants