Pointing a Windows Application to Node executable in WSL

[DamianRivas]

• Your Windows build number: (Type ver at a Windows Command Prompt)

Microsoft Windows [Version 10.0.16299.371]

• What you're doing and what's happening: (Copy&paste specific commands and their output, or include screen shots)

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.

• What's wrong / what should be happening instead:

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?

[onomatopellan]

Take a look at this
https://blogs.msdn.microsoft.com/commandline/2017/10/27/running-node-js-on-wsl-from-visual-studio-code/

[DamianRivas]

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.

[onomatopellan]

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.

microsoft/vscode#13138

[bardware]

When I try ot start Quokka

How do you start Quokka? How did you start code?

[DamianRivas]

To recreate the problem you can just install the Quokka extension and open up a JavaScript file in VS Code. Then, press ctrl + K, Q.
If you are using node through WSL, it won't work.

[rfgamaral]

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.

[therealkenc]

IMO this is something that should be addressed by Quokka and not WSL.

Pretty much. There's no WSL actionable here.

[jrock2004]

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.

[therealkenc]

This is feature request wallabyjs/quokka#187. There is no WSL actionable (a bug in Linux syscall emulation) identified here.

Windows should be able to see what is on the Linux path and add it to its own.

That's #1823