Live data from Hacker News

PhantomJS: Archiving the project, suspending development

github.com

91–100 of 138 posts

Re: PhantomJS: Archiving the project, suspending development

#91
post #6

I still think it's premature. There is still couple of fields PhantomJS is better than Headless Chrome. Notably proxy support, and API aviability.

That's not really true. You can use proxies with Headless Chrome using the --proxy-server command line parameter. And the API is richer that PhantomJS. See the underlying API documentation here: https://chromedevtools.github.io/debugger-protocol-viewer/to....

Re: PhantomJS: Archiving the project, suspending development

#92
Timeline of what lead to this, from what I could gather:

• phantomjs is 7 years old, @pixiuPL has been contributing for about 2 months

• @ariya didn't respond to his requests for owner level permissions

• @pixiuPL published an open letter to the main page of phantomjs.org https://github.com/ariya/phantomjs/issues/15345

• the stress leads @ariya to close the repo.

• @pixiuPL intends to continue development on a fork

This is a good reminder of why non-technical skills are so important in OS and in general.

Re: PhantomJS: Archiving the project, suspending development

#93

Timeline of what lead to this, from what I could gather: • phantomjs is 7 years old, @pixiuPL has been contributing for about 2 months • @ariya didn't respond to his requests for owner level permissions • @pixiuPL published an open letter to the main page of phantomjs.org https://github.com/ariya/phantomjs/issues/15345 • the stress leads @ariya to close the repo. • @pixiuPL intends to continue development on a fork T…

[deleted]

Re: PhantomJS: Archiving the project, suspending development

#94

Timeline of what lead to this, from what I could gather: • phantomjs is 7 years old, @pixiuPL has been contributing for about 2 months • @ariya didn't respond to his requests for owner level permissions • @pixiuPL published an open letter to the main page of phantomjs.org https://github.com/ariya/phantomjs/issues/15345 • the stress leads @ariya to close the repo. • @pixiuPL intends to continue development on a fork T…

I don't know man, but look at @pixiuPL's commits https://github.com/ariya/phantomjs/commits?author=pixiuPL

Especially his own commits (non-merge commits)

Re: PhantomJS: Archiving the project, suspending development

#95
post #94

Timeline of what lead to this, from what I could gather: • phantomjs is 7 years old, @pixiuPL has been contributing for about 2 months • @ariya didn't respond to his requests for owner level permissions • @pixiuPL published an open letter to the main page of phantomjs.org https://github.com/ariya/phantomjs/issues/15345 • the stress leads @ariya to close the repo. • @pixiuPL intends to continue development on a fork T…

I don't know man, but look at @pixiuPL's commits https://github.com/ariya/phantomjs/commits?author=pixiuPL Especially his own commits (non-merge commits)

What about them?

Re: PhantomJS: Archiving the project, suspending development

#96

Some people are mentioning headless Chromium, so I wanna mention another tool I've used to replace some of phantomjs' functionality: jsdom [0]. It's much more lightweight than a real browser, and it doesn't require large extra binaries. I don't do any complex scrapping, but occasionally I want to pull down and aggregate a site's data. For most pages, it's as simple as making a request and passing the response into a…

One question I've had recently is how to scrape out a Javascript object out of HTML source. With server-side react + redux, I've wanted to be able to scrap out the serialised var __STATE__ = {...} object to JSON, from nodejs. Best solution I cobbled together was to basically eval() the JS source, which I know is far from ideal.

You can use the vm module [0] to securely execute the code.

[0] https://nodejs.org/api/vm.html

Re: PhantomJS: Archiving the project, suspending development

#97
post #95
post #94

Earlier quoted context omitted.

I don't know man, but look at @pixiuPL's commits https://github.com/ariya/phantomjs/commits?author=pixiuPL Especially his own commits (non-merge commits)

What about them?

He committed:

- Removing one whitespace and adding an unnecessary file https://github.com/ariya/phantomjs/commit/98272b9752b2d505f7...

- Conflicted files https://github.com/ariya/phantomjs/commit/63a69d9e2e9c31baab...

- Personal build env https://github.com/ariya/phantomjs/commit/d57ff74f36c5b79d82...

- Deleted the whole project while changing cloud provider https://github.com/ariya/phantomjs/commit/a242fb8d605d9aa4af...

- then re-adding the whole project again https://github.com/ariya/phantomjs/commit/ddaaa09785d453e415...

and other weird/careless commits

Re: PhantomJS: Archiving the project, suspending development

#98
post #95
post #94

Earlier quoted context omitted.

I don't know man, but look at @pixiuPL's commits https://github.com/ariya/phantomjs/commits?author=pixiuPL Especially his own commits (non-merge commits)

What about them?

Make of it what you will but they appear to be a bunch of commits that amount to removing white space or adding/removing comments with messages like "Code refactoring". It looks a lot like someone trying to get their git blame count up by any means other than writing actual code.

Re: PhantomJS: Archiving the project, suspending development

#99

Timeline of what lead to this, from what I could gather: • phantomjs is 7 years old, @pixiuPL has been contributing for about 2 months • @ariya didn't respond to his requests for owner level permissions • @pixiuPL published an open letter to the main page of phantomjs.org https://github.com/ariya/phantomjs/issues/15345 • the stress leads @ariya to close the repo. • @pixiuPL intends to continue development on a fork T…

I guess so. But it just seems like this person is done. People are allowed to be done. And really, communication skills on the part of community members should be emphasized as well.

Edit: after reading some more of the reasoning and the discussions that led to this, I’m even less inclined to blame the maintainers for closing the project. People wanted more than it could give. If this other person really wants to take on that burden with a fork, by all means.

Re: PhantomJS: Archiving the project, suspending development

#100
post #90

Shoot, I was just planning to use this for generating PDFs out of a URL on nodejs. Does anyone know of any other library / module out there that is good at this?

You can generate pdfs with headless Chromium/Chrome pretty easily. chromium-browser --headless --disable-gpu --print-to-pdf=output_file_name.pdf file:///path/to/your/html

Sadly you get 0 control over headers and footers of the output PDF, meaning you get lovely crappy page numbers around the place with no way to turn them off. This is why, sadly, I have to keep my command line markdown -> pdf converter (https://www.npmjs.com/package/mdpdf) using Phantomjs.

So this does work for very basic pdf printouts, but so far phantom is the only tool that offers full control over the PDF output. Even down to things like margins, paper size, etc.

Post reply on HN