Skip to content
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

Compatibility problems with Windows #21

Open
jmhomedes opened this issue May 28, 2016 · 0 comments
Open

Compatibility problems with Windows #21

jmhomedes opened this issue May 28, 2016 · 0 comments

Comments

@jmhomedes
Copy link
Contributor

jmhomedes commented May 28, 2016

Running the plugin on Windows 8 x64 throws an error ENOENT when trying to spawn phantomjs. It seems like is a known issue with child_process.spawn not respecting EXTPATH, as mentioned here: nodejs/node-v0.x-archive#2318

Then I tried to change the name passed to spawn process to 'phantomjs.cmd' and it worked fine. As this is not a X-platform solution, I thought on requiring explicitly phantomjs in project, taking the opportunity to require latest phantomjs-prebuilt module and calling spawn with require('phantomjs-prebuilt').path

I tried it on Win8x64 and Ubuntu 14.04 and working fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant