-
Notifications
You must be signed in to change notification settings - Fork 43
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
Failing to install PhantomJS 2.0.0 #12
Comments
Hey Olly! Thanks for reporting the issue.
Possible solutions:
I think the best solution would be to simply revert it. What do you think? |
Ok. I leave the issue open for others running into this. Update: Referencing: |
Faced with the same problem .. Thanks for the clarification. |
Any update on this? I'm getting the same error when using dev-master |
For further info, this is what I'm getting when attempting to install my project using Laravel Forge: Generating autoload files
|
No update on this. They are still in this disastrous state of the PhantomJS project. It's quite impressive how such a widely used project gets stuck, when the Continuous Integration stops compiling / working and the maintainer starts to work on other projects. It seems that Travis-CI is not able to build PhantomJS, because the boxes provide only ~4GB memory. PhantomJS is build on a patched Qt framework and this build really draws on memory and build time. I think there will be no progress in this area, unless they upgrade their CI package at Travis to professional (in order to get more mem) or switch their CI service AND more important: the two maintainers find more time to get the project back on track. They could also decide to split out the framework build and pull the dependencies in. |
+1 I'm encountering the same issue and indeed thank you @jakoch for the details about the issue ! |
Same problem here, this is my error
|
same problem |
Unfortunately the situation of the phantomjs project itself is unchanged.. :( |
it would propose marking 2.0 branch as dev since it is not really 2015-09-04 19:52 GMT+02:00 Jens A. Koch notifications@github.com:
|
Same problem here, but I don't need 2.0.0 - I'll lock to 1.9.8 for the time being. Thanks for your work on this. |
Yes, locking to 1.9.8 is the right thing. I still hope that the Phantom team gets another release out this year, but Ariya spends his limited time working on Esprima. :/ (By the way: I've seen your nickname a couple of times over at SO and read your "I ♥ PHP" tutorial. |
@jakoch, thanks! It was more work than I expected, certainly. I don't do so much work on it now, as it is doesn't get as much attention/feedback as I thought it might - I think it needs some promotion. Might do some more work on it, or a follow-up tutorial, in the future 😄 |
Update: seems PhantomJS v2.1 is slowly cooking up.. |
removed the hardcoded latest version from getVersion() and replaced it by a call to the newly added getLatestPhantomJsVersion() issue #12
Update: PhantomJS v2.1.1 was released - http://phantomjs.org/download.html I've adjusted the installer to fetch the latest version and tagged a new release: Best, Jens |
Hi there
I'm using this package with laravel, deployed via rocketeer. It has worked flawlessly up until PhantomJS was updated to 2.0.0. Now I'm seeing the following errors when composer runs its
post-install
commands:Please let me know if you need any further information.
Thanks!
EDIT: I'm using dev-master, will drop version for now.
The text was updated successfully, but these errors were encountered: