-
Notifications
You must be signed in to change notification settings - Fork 5.7k
Please add notice that PhantomJS is abandoned #15105
Comments
@csvan There's a 2.5 beta out. Give it a try! |
Now we can - https://github.com/GoogleChrome/puppeteer This is a meta issue for final words. I would like to give thanks to all who have been developing this project so far:
It was an amazing time! You can be sure that Google DevTools can handle and develop With this message, no more commits will be pushed here. The development has been stopped for good and all. |
Thank you very much Vitaly, Ariya and PhantomJS gang. Your work has enabled new possibilities and solutions for countless people. Want to say wish you all the best in your next huge undertaking!! |
PhantomJS has been crucial in projects I have been involved in over the years. We still have it in production for some systems and it is likely to be spinning there for quite some time.. Thank you @vitallium and all the contributors for your work, it has made a difference for thousands of devs. |
Thanks for your great job guys. |
Thank you PhantomJS! |
Thank you very much for all the work you have done in recent years. You have contributed to the evolution of the use of web browsers in a considerable way (in terms of application tests, scrapping, supervision ...) I have only one regret is that version 2.5 which led to the management of "promises" will never come out in stable version. My adminstration will continue to use PhantomJS version 2.1.1 for a long time with all possible javascript patches (without having ever contributed to the project). Thank you and congratulations. |
For things like promises, we use this ES6 shim: https://github.com/paulmillr/es6-shim We use Phantom for headless unit testing of Jasmine tests, so we have control of what assets can be added to the page. |
Thank you PhantomJS guys! |
Thank you PhantomJS, and welcome Chrome headless era |
PhantomJS helped me a lot, thanks!!! |
@vitallium Since this issue is still open and there is no notice on either github or phantomjs.org, is the abandonment uncertain? |
@bughit I stopped working on PhantomJS two months ago. |
@vitallium I understand that your stepping down is certain, it was unclear if there was some significance to this being open and the absence of notice. |
@bughit We decided to not do that. Anyone can catch up and continue developing the project ;-) |
Thank you guys for your hard work! 👍 |
We used PhantomJS for several years. Was instrumental in getting us where we are today. RIP |
I see there are quite a few new commits by @pixiuPL recently. Does that mean PhantomJS is living again? ;) |
Adding on to @yan12125's comment, did you guys see that PhantomJS homepage now shows v2.1.3 latest release instead of v2.1.1 ?! - @pixiuPL's commits are still coming in 😱 EDIT - https://groups.google.com/forum/#!topic/phantomjs/6Va4F9nlGeU |
Well, to be completely honest with you all, I must admit that currently Im the only one dev working on PhantomJS daily. |
This is great news for a lot of people! Thank you very much pixiuPL! 😄 |
Any plan for version > 2.1.1 is effectively abandoned. Please see #15344 for more details. |
There are no feature tests which currently use `js: true`. The only one that needs it (in `spec/features/admin/manage_workshop_attendances_spec.rb`) is currently skipped, and also doesn't work with the current Poltergeist/PhantomJS setup anyway. PhantomJS is currently unmaintained: ariya/phantomjs#15105 (comment). It looks like the next thing to do is to look into using headless Chrome, which will be addressed in a future PR.
There are no feature tests which currently use `js: true`. The only one that needs it (in `spec/features/admin/manage_workshop_attendances_spec.rb`) is currently skipped, and also doesn't work with the current Poltergeist/PhantomJS setup anyway. PhantomJS is currently unmaintained: ariya/phantomjs#15105 (comment). It looks like the next thing to do is to look into using headless Chrome, which will be addressed in a future PR.
I think it would be good to provide a link to the following if no further maintenance is planned. Chrome Headless has been out for all major platforms for some time now and is already seeing major adaption, as predicted by the original maintainer.
https://groups.google.com/forum/#!topic/phantomjs/9aI5d-LDuNE
The text was updated successfully, but these errors were encountered: