-
Notifications
You must be signed in to change notification settings - Fork 827
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
Pointing a Windows Application to Node executable in WSL #3112
Comments
I'm aware of running the debugger through WSL, but I don't think that applies here. I didn't create the extension and the way the extension works is you have to point it to a node executable in its configuration file as stated in the docs that I linked. |
I think in your case it would be worth trying VScode Linux version inside WSL. You will need VcXsrv and latest Windows Insider build or wait for April Update (version 17134) available in the next weeks. |
How do you start Quokka? How did you start code? |
To recreate the problem you can just install the Quokka extension and open up a JavaScript file in VS Code. Then, press |
Here's the same issue (from OP) on Quokka's repository: wallabyjs/quokka#187 IMO this is something that should be addressed by Quokka and not WSL. I mean, WSL already provides all the means for interoperability. It's up to applications themselves to use the necessary tools to glue all the things. |
Pretty much. There's no WSL actionable here. |
I know this is an old closed issue, but why is this on Quokka, @therealkenc? WSL was built to give Windows Linux tools. I believe this is a WSL issue. Windows should be able to see what is on the Linux path and add it to its own. |
This is feature request wallabyjs/quokka#187. There is no WSL actionable (a bug in Linux syscall emulation) identified here.
That's #1823 |
ver
at a Windows Command Prompt)Microsoft Windows [Version 10.0.16299.371]
I am trying to use Quokka for live debugging of my code in VS Code. When I try ot start Quokka, I get:
Can not start node.js process (node), make sure your system has node.js installed.
I do have Node installed, in WSL, through nvm:
The Quokka docs shows that we can point Quokka to any node executable for it to use: https://quokkajs.com/docs/configuration.html#nodejs-version.
Obviously, my node executable is in the WSL file system, so I don't think it's safe to point Quokka directly at it.
Is there a safe way to establish a line of communication between Windows and Linux executables?
The text was updated successfully, but these errors were encountered: