Chrome and Firefox gaining headless modes is the ultimate goal Phantom could've achieved. So I consider it a complete success. Kudos to all contributors.
Sadly, Chrome won't support extensions: https://bugs.chromium.org/p/chromium/issues/detail?id=706008
PhantomJS: Archiving the project, suspending development
101–110 of 138 posts
Re: PhantomJS: Archiving the project, suspending development
#102Re: PhantomJS: Archiving the project, suspending development
#103Earlier quoted context omitted.
Does headless chrome do PDF generation? That's the only thing I'm using phantom for at the moment.
Yes. It's really easy to do using [puppeteer]( https://github.com/GoogleChrome/puppeteer ). The 2nd or 3rd example is PDF.
Re: PhantomJS: Archiving the project, suspending development
#104Timeline 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
#105Earlier quoted context omitted.
Does headless chrome do PDF generation? That's the only thing I'm using phantom for at the moment.
Yes. It's really easy to do using [puppeteer]( https://github.com/GoogleChrome/puppeteer ). The 2nd or 3rd example is PDF.
Re: PhantomJS: Archiving the project, suspending development
#106Timeline 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)
I couldn't find a single one containing any meaningful code changes. The closest one is a81a38f[1] which seems to introduce bugs - removing open file check, plus a hanging if clause.
Sounds like it's either an elaborate prank, or the guy has no grounding on reality.
[1] https://github.com/ariya/phantomjs/commit/a81a38ffabe2cea715...
Re: PhantomJS: Archiving the project, suspending development
#107Chrome and Firefox gaining headless modes is the ultimate goal Phantom could've achieved. So I consider it a complete success. Kudos to all contributors.
Re: PhantomJS: Archiving the project, suspending development
#108Timeline 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)
How did his changes even make it to the repo. There are commits adding and deleting whitespace with the disguised commit message of "Refactoring Code". I have no doubt on why ariya couldn't work with him.
Re: PhantomJS: Archiving the project, suspending development
#109Earlier quoted context omitted.
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 could use a parser like esprima or its equivalent from the babeljs ecosystem on the JS source instead and just find the global variable with name `__STATE__` and just eval its init expression. Cheaper, more secure, more direct than actually running the JS.
Re: PhantomJS: Archiving the project, suspending development
#110Earlier 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)
Exactly. I mean look at his commits. Look at this file: https://github.com/ariya/phantomjs/blob/master/package.json (He created a commit only to add his how name as a contributor to package.json, which is the only name in package.json). How did his changes even make it to the repo. There are commits adding and deleting whitespace with the disguised commit message of "Refactoring Code". I have no doubt on why ariya co…