-
Notifications
You must be signed in to change notification settings - Fork 436
2.0 #288
Comments
AFAIK, the phantomjs 2.0 release is not complete yet. We usually get a note from the phantomjs team when they're ready to roll new versions out more widely. For updates on the release process, see: |
Yeah, just saw that PR fail and why it did. Thank you! |
It's officially out now. Official website has it ready to download. |
We are still blocking on the release on linux binaries. |
also, the current binaries appear to be completely busted on newer versions of OSX, though the discussion on this bug ariya/phantomjs#12630 suggest that this will be fixed before 2.0 is blessed. |
That makes sense. Thanks for keeping on top of this! |
ariya/phantomjs#12897 - Linux binaries are still missing |
It looks like the PhantomJS team was not able to build working OSX and Linux binaries of version 2.0, and has decided to abandon them and try to fix this in 2.1. Given that this package is supposed to be a platform-independent binary installer, this puts us in a difficult position. We can't release an NPM package that doesn't work. We will have to wait until 2.1. |
@nicks it's actually getting fixed in 2.0.1 not 2.1. See ariya/phantomjs#12948 and ariya/phantomjs#12902. So while it's sad that we don't get 2.0.0 goodness the wait won't be that long either :). |
Do you guys have any luck running the 2.0.0 on OSX (10.10.3)? When I run it, the output is simply this
Or any other process number... Any ideas? |
I installed phantomjs 2.0.0 via Homebrew and it works fine though I'm on OS X 10.10.2. |
Just installed via homebrew instead of using the standalone bin. The brew version works properly, the standalone does not appear to work at all. Thanks! |
I had success unpacking the downloadable binary with |
Could travis-ci's linux binary be used travis-ci/travis-ci#3225 (comment) ? |
Anything happening here? |
@stevenvachon I have a fork that is working with 2.0 here https://github.com/dtothefp/phantomjs for OSX |
upgrade? |
+1 |
@Lochlan What is the reason not supporting windows in your fork? Installation fails quite hard. |
I see there's a |
@flesler nope. This tag was failed experiment. If you really want to use 2.0 version, just try another package, like: https://www.npmjs.com/package/phantomjs2 https://www.npmjs.com/package/phantomjs2.0 and others |
@tregusti The reason I don't support Windows in my fork is that I don't have to support Windows machines, either at work or in my personal life. If you would like to add Windows support and open a pull request I will be happy to accept it, or you are of course free to make your own fork as well. |
👍 |
New tracking issue: ariya/phantomjs#13822 |
@Lochlan now that 64 bit binaries are out, and 32 bit binaries are just around the corner, can we expect phantomjs 2.0 support soon? |
@mikesherov unfortunately, they are not out yet. They've just found a way to produce them on a sufficiently performant machine. |
It seems the following was released. Is that what this issue has been waiting for?
|
yay! |
Still no 32-bit version though? |
@mikesherov phantomjs-2.1.0-linux-i686.tar.bz2 |
PhantomJS 2.1is official: On Sun, Jan 24, 2016, 9:46 PM John Yani notifications@github.com wrote:
|
+1000 |
Just tested this on Mac OS 10.11.2 and Windows 10 and it works great 😄 The long wait is over! Thanks! |
So what's the guidance on the npm package. I see the deprecation message for the |
phantomjs-prebuilt. Its in the readme! On Thu, Jan 28, 2016 at 5:49 PM John-David Dalton notifications@github.com
|
That's the Medium package, no? I'm looking for the official one. |
IDK if there is one, but that would be interesting |
Both |
http://phantomjs.org/release-2.0.html
PhantomJS 2.0 was released last week. Any chance a new release is in the cards?
The text was updated successfully, but these errors were encountered: