-
Notifications
You must be signed in to change notification settings - Fork 434
phantomjs.path is null #533
Comments
I've just experienced the same issue on version phantomjs-prebuilt v2.1.5, and phantomjs binary v2.1.1. Update: Just tried installing all of the versions from 2.1.3 to 2.1.7 into a temp folder, and all show the path property populated. Therefore there must be something about the installation process causing an issue. Eventually fixed. Individually everything was working fine. As a larger package.json it was failing silently due to running out of memory, presumably for the spawned phantomjs installation. This was on 1Gb Digital Ocean box. |
@JonForest You're right I have only @JonForest In the directory
|
@igorissen It really should be called. It's spawned as a separate process, so something is stopping that working. In my case it's memory, but I couldn't speculate usefully for you. |
@JonForest There is always one file I have also noticed that there is no
|
I've run into this as well, installing phantomjs-prebuilt by itself seems to work, but subsequent fresh installs do not (i.e. when running `rm -rf node_modules && yarn install) |
Have the same issue on Mac. Managed somehow to get it working in one project, but can't repeat it for another project. could anybody help with the step how to get it installed correctly? |
Hi,
I have an issue that points to an issue with
child_process.execFile(...)
(Bad argument). So I have put som logs to show what is the path of phantomjs binary.The path is
null
.I'm using node
v5.10.1
, phantomjs-prebuiltv2.1.7
and phantomjs binaryv2.1.1
The text was updated successfully, but these errors were encountered: