Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Issues installing with phantomjs version 1.8.2-1 #17

Closed
smistry-toushay opened this Issue Mar 20, 2013 · 22 comments

Comments

Projects
None yet

Getting the following error message:

Running PhantomJS...ERROR
>> In order for this task to work properly, PhantomJS must be installed locally
>> via NPM. If you're seeing this message, generally that means the NPM install
>> has failed. Please submit an issue providing as much detail as possible at:
>> https://github.com/gruntjs/grunt-lib-phantomjs/issues
Warning: PhantomJS not found. Use --force to continue.

Looking for phantomjs in node_modules/phantomjs/lib/phantom/bin/phantomjs. Looks like phantomjs version 1.8.2-1 installs it to node_modules/phantomjs/bin/phantomjs

No more lib/phantom folder:

node_modules/phantomjs/lib/phantom/bin/phantomjs

vs.

node_modules/phantomjs/bin/phantomjs

TrejGun commented Mar 20, 2013

this is issue of phantomjs Obvious/phantomjs#15

cd node_modules/phantomjs/tmp/
cp -r phantomjs-1.8.2-macosx ../lib
cd ../lib
mv phantomjs-1.8.2-macosx phantomjs

chmod 755 :)

@jasonsanjose jasonsanjose referenced this issue in adobe/brackets Mar 20, 2013

Closed

Re-enable jasmine tests #3193

@ctapbiumabp When I follow your steps, I get:

Running PhantomJS...ERROR
>> 0 [ '' ]
Warning: PhantomJS exited unexpectedly with exit code null. Use --force to continue.

Aborted due to warnings.

When I add a grunt.log to the 'else' error block in phantomjs.js, I get:

Fatal error: Property 'log' of object #<Object> is not a function

I hit this today as well. I changed our package.json to include phantomjs@1.8.1-1 as a hack. See adobe/brackets#3193.

TrejGun commented Mar 21, 2013

@tmartensen i have exactly the same for qunit but simple js files works ok

TrejGun commented Mar 21, 2013

@jasonsanjose works like magic

@tmartensen I got the same error. Looks like the phantomjs-1.8.2-macosx.zip archive in tmp doesn't properly unzip. Extract it yourself before following the steps from @ctapbiumabp.

Yep. That way works, but I prefer the workaround presented by @jasonsanjose because our app gets deployed into CI.

I tried setting phantomjs to 1.8.1-1 on my package.json, installing again but i'm still getting the PhantomJS not found problem.

arhea commented Mar 29, 2013

I just had the same issue.

Running "qunit:all" (qunit) task
Testing tests/index.html
Running PhantomJS...ERROR
>> In order for this task to work properly, PhantomJS must be installed locally
>> via NPM. If you're seeing this message, generally that means the NPM install
>> has failed. Please submit an issue providing as much detail as possible at:
>> https://github.com/gruntjs/grunt-lib-phantomjs/issues
Warning: PhantomJS not found. Use --force to continue.

Aborted due to warnings.
Member

jsoverson commented Mar 31, 2013

Until this gets handled in Obvious/phantomjs, I've removed the version range for phantomjs so that the last known good version will install.

This is to get past issue 38 in Obvious/phantomjs.

@cowboy, can you publish a new version or add me as an author in npm?

I had the same issue, using grunt with yeoman. From my working directory, I did the following to fix it:

cd node_modules/grunt-mocha/node_modules/grunt-lib-phantomjs
npm install phantomjs
cd node_modules/phantomjs/tmp
rm -R phantomjs-1.8.2-macosx
unzip phantomjs-1.8.2-macosx.zip 
cp -R phantomjs-1.8.2-macosx ../lib/phantom

devinsba commented Apr 1, 2013

My fix was to modify the package.json in place to match this commit until a new version is in npm.

https://github.com/devinsba/heroku-test-app/blob/master/fixPhantomJS.sh

@shaagerup your fix worked for me w/ phantomjs 1.9.x installed and latest yeoman.

Thanks!

bonpixel commented Apr 3, 2013

@shaagerup you win sir, you simply win...Thanks very much :)

orald commented Apr 3, 2013

@shaagerup you simply win sir!. Thanks...

I've got phantomjs at 1.9, but still get a grunt build error.

devinsba commented Apr 3, 2013

@nouveller Have you used the workaround described by shaagerup above? That should fix any issue related to this thread. If you have and still have issues I would suggest creating a new issue. Also providing the error message would be helpful

Member

jsoverson commented Apr 4, 2013

Tested phantomjs 1.9.0-1 on multiple environments with pr #19 and all seems to work well. I just published 0.3.0 to npm.

Let us know of any other issues, I'm working on contrib-jasmine now and will get to contrib-qunit as soon as I can.

Member

jsoverson commented Apr 4, 2013

@glan, are there still issues with the new version?

Please post comments with environment and version information so we know where to target.

glan commented Apr 4, 2013

@jsoverson It was caused by grunt-contrib-jasmine 0.3.x, we upgraded to 0.4.x and that seem to help. Was just super frustrating all our builds failed.

wwalser commented Apr 5, 2013

Upon running yo webapp for the first time tonight I've run into this issue. Digging in a bit it looks like grunt-lib-phantomjs 0.2.0 was installed as a dependency of grunt-mocha 0.2.3.

This ended with "phantomjs": "~1.8.1" in the grunt-lib-phantomjs package.json.

This pull request appears to resolve my issue: kmiyashiro/grunt-mocha#57

Thanks guys!

Edit: Actually… until this PR lands, how do I resolve this manually? Is the manual extraction of the zip the recommended workaround?

@joelarson4 joelarson4 referenced this issue in joelarson4/CharFunk Apr 6, 2013

Closed

Cannot run qunit as part of grunt process #2

kevva referenced this issue in yeoman/generator-chrome-extension Apr 7, 2013

@jreading jreading referenced this issue in gruntjs/grunt-init-jquery May 8, 2013

Closed

Fix for phantomjs@1.8.1-1 #8

@rbarreca rbarreca referenced this issue in karma-runner/karma-phantomjs-launcher Jun 7, 2013

Merged

fix: Depend on PhantomJS 1.9 to fix path issue and be at latest stable. #4

npm set strict-ssl false

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment