If you've followed Sarke's answer and are still having trouble Honestly, I'm not sure why that fixes it, nor why WebStorm doesn't automatically use the default shell. This worked for me, having installed WebStorm via the Pop Shop. If this doesn't work for you (and nor does Sarke's answer), skip to the second part of my answer. Simply replace node with php in the content and filename: #!/usr/bin/env shįlatpak-spawn -host php your WebStorm detects the node interpreter, but won't let you use it via terminalįor anyone stumbling onto this in the future, and your flatpak installation detects a node interpreter (using Shift+F10 works), but using node or npm via WebStorm's terminal doesn't work, you may be able to fix that by switching the default terminal in WebStorm from sh to bash:įile > Settings > Tools > Terminal then set Shell Path to /bin/bash Of note is this same solution works for PhpStorm and the php interpreter. Personally, I make the file ~/bin/flatpak-node, but you can put it anywhere in the home directory. It works because the executable we created is in the home directory, and flatpak-spawn can run the command as if it was on the host (outside of the sandbox).
This will create an executable file called flatpak-node in your home directory, with this content: #!/usr/bin/env shįlatpak-spawn -host node will tell Flatpak to run the node binary on the host and pass along any parameters. Run these two commands in shell: printf '#!/usr/bin/env sh\nflatpak-spawn -host node > ~/flatpak-nodeįile > Settings > Languages & Frameworks > Node.js and NPM (or TypeScript)Īnd set the Node Interpreter to ~/flatpak-node.
However, there is a way to get around this, by having flatpak run the host binary using the flatpak-spawn.ġ. Flatpak is sandboxed, so it cannot directly run anything that is on the host, outside of the user's home directory.
0 kommentar(er)
