Error when runs from WSL
See original GitHub issuePaths are not working with WSL.
To Reproduce Steps to reproduce the behavior:
- Create a project with Vite inside WSL
- Opened it on VS Code using the Remote - WSL extension.
- Install
click-to-component
and add the configs - Run de project
- Click on the secondary button and show the context menu with components
- Click on <App> component
- Show an error on VSCode
- If click on [Yes] button, show this message
- This is the message that shows the console in Chrome
Expected behavior Open in VSCode without error
Desktop:
- OS: Windows 10 21H2
- Browser: Chrome
- Version: Version 100.0.4896.127 (Official Build) (64-bit)
- WSL: Version 2
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:10 (1 by maintainers)
Top Results From Across the Web
Troubleshooting Windows Subsystem for Linux | Microsoft Learn
Instead run wsl.exe from PowerShell Core, or Command Prompt. Error: Windows Subsystem for Linux has no installed distributions.
Read more >WSL2-Error: A connection attempt failed on Windows ... - GitHub
After updating to Windows 19555 I get the following error, when starting WSL: A connection attempt failed because the connected party did ...
Read more >Docker Desktop WSL 2 backend on Windows
Ensure the distribution runs in WSL 2 mode. WSL can run distributions in both v1 or v2 mode. · When Docker Desktop starts,...
Read more >WSL Something Went Wrong Windows 11 Error: 6 Rigorous ...
Press the Windows + R keys to open the Run dialog box, then type cmd.exe. · Right-click on the title bar, and choose...
Read more >Multiple Errors when Running Bun via WSL - Stack Overflow
Furthermore, if you are getting an error for NotSameFileSystem , then you need to defer to using a different style for installations. This...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’ve voted for https://github.com/microsoft/vscode-remote-release/issues/4779!
In the meantime, I think we’re forced to close this issue **until the browser supports a
${protocol}://...
that this library canwindow.open(url)
with 😦When that’s ready, instead of
editor
there’ll be a prop likesourceToURL({ editor, source }): string
that you can use to craft a working URL.I’ve copied the path from File Explorer
Add put on browser address bar like this:
vscode://file//wsl$/Ubuntu/home/juanmartinez/DEIN/scrimba-react-vite/src/App.jsx:11:9
But happen me the same to you, open it another ‘local’ instance, instead ‘wsl-remote’
Seems to be that we are gonna need to wait until
vscode-remote://
was supported on the browser 😥