Open erelsgl opened 8 years ago
Thanks for raising this. Can you add a screenshot of what it looks like?
I try to upload the screenshot to github but it does not work. I can send you by email if you want.
I had a similar problem. The plugin couldn't find my node executable, and the result was a black screen. My problem was that I didn't have a system level node and only use nvm (I opened a feature request here #61 )
You can test if this is the problem by going to your terminal and run: which node
and add the outputted path as the path to your node executable in the settings for this plugin.
having the same issue, using:
Running test from https://github.com/stmllr/node-test-package with the following result (context information activated):
I can agree with @gustavnikolaj - I experienced the same issue due to the node location being incorrect. It would be nice if the package called node without using it's explicit path (as it's likely already declared in the systems PATH variable).
Just for clarity, I'm using Fedora 25 (Linux) and the default node directory is /usr/bin/node.
Thanks @andyrichardson. I'll run some more tests, but I think Atom plugins don't have access to the calling environment, including the user's $PATH
. Do you have any other suggestions on how to fix it?
As a starting point, I'll add an explicit error message if Node can't be found.
@rprieto off the top of my head, I know atom-script calls environment variables using bash in Linux and Mac.
/bin/bash -c mocha $args
Something like that might work and you can be sure that bash is in the bin folder and make use of environment variables.
I created a trivial test in my test folder:
When I click Ctrl+Alt+M, I see a pink title "Mocha test results...". Below it, there is a black empty window. This remains like this indefinitely.
Mocha runs fine when I run it from the root of my project.
Here are the relevant lines from my packages.json file: