PhantomJS vs Chromeless Comparison | StackShare | StackShare

Chromeless vs PhantomJS

Overview

PhantomJS

Stacks1.2K

Followers430

Votes18

GitHub Stars29.5K

Forks5.7K

Chromeless

Stacks13

Followers29

Votes0

Chromeless vs PhantomJS: What are the differences?

Chromeless: 🖥 Chrome automation made simple. Runs locally or headless on AWS Lambda. Chrome automation made simple. Runs locally or headless on AWS Lambda; PhantomJS: Scriptable Headless WebKit. PhantomJS (www.phantomjs.org) is a headless WebKit scriptable with JavaScript. It is used by hundreds of developers and dozens of organizations for web-related development workflow.

Chromeless and PhantomJS can be categorized as "Headless Browsers" tools.

Chromeless and PhantomJS are both open source tools. PhantomJS with 26.9K GitHub stars and 5.7K forks on GitHub appears to be more popular than Chromeless with 13.2K GitHub stars and 602 GitHub forks.

Advice on PhantomJS, Chromeless

Ankur

Software Engineer

Dec 4, 2019

Needs advice

I am using Node 12 for server scripting and have a function to generate PDF and send it to a browser. Currently, we are using PhantomJS to generate a PDF. Some web post shows that we can achieve PDF generation using Puppeteer. I was a bit confused. Should we move to puppeteerJS? Which one is better with NodeJS for generating PDF?

73k views73k

Comments

Detailed Comparison

PhantomJS	Chromeless
PhantomJS is a headless WebKit scriptable with JavaScript. It is used by hundreds of developers and dozens of organizations for web-related development workflow.	Chrome automation made simple. Runs locally or headless on AWS Lambda.
Multiplatform, available on major operating systems: Windows, Mac OS X, Linux, and other Unices; Fast and native implementation of web standards: DOM, CSS, JavaScript, Canvas, and SVG. No emulation; Pure headless (no X11) on Linux, ideal for continuous integration systems. Also runs on Amazon EC2, Heroku, and Iron.io; Easy to install: Download, unpack, and start having fun in just 5 minutes	-
Statistics
GitHub Stars 29.5K	GitHub Stars -
GitHub Forks 5.7K	GitHub Forks -
Stacks 1.2K	Stacks 13
Followers 430	Followers 29
Votes 18	Votes 0
Pros & Cons
Pros 13 Scriptable web browser 3 Depends on QT 2 No ECMAScript 6	No community feedback yet
Integrations
FreeBSD macOS Windows Linux	Serverless AWS Lambda

What are some alternatives to PhantomJS, Chromeless?

Playwright

It is a Node library to automate the Chromium, WebKit and Firefox browsers with a single API. It enables cross-browser web automation that is ever-green, capable, reliable and fast.

Puppeteer

Puppeteer is a Node library which provides a high-level API to control headless Chrome over the DevTools Protocol. It can also be configured to use full (non-headless) Chrome.

HeadlessTesting

Headless Browser Cloud for Developers. Connect your Puppeteer and Playwright scripts to our Cloud. Automated Browser Testing with Puppeteer and Playwright in the Cloud.

jsdom

It is a pure-JavaScript implementation of many web standards, notably the WHATWG DOM and HTML Standards, for use with Node.js. In general, the goal of the project is to emulate enough of a subset of a web browser to be useful for testing and scraping real-world web applications.

CasperJS

CasperJS is a browser navigation scripting & testing utility written in Javascript for PhantomJS or SlimerJS.

Splash

It is a headless browser that executes JavaScript for people crawling websites. It is open source and fully integrated with Scrapy and Portia. You can also use its API to integrate with any project that needs to render JavaScript pages.

SlimerJS

It allows you to manipulate a web page with an external Javascript script: opening a webpage, clicking on links, modifying the content... It is useful to do functional tests, page automation, network monitoring, screen capture etc.

Serverless Chrome

The aim of this project is to provide the scaffolding for using Headless Chrome during a serverless function invocation. Serverless Chrome takes care of building and bundling the Chrome binaries and making sure Chrome is running when your serverless function executes. In addition, this project also provides a few "example" handlers for common patterns (e.g. taking a screenshot of a page, printing to PDF, some scraping, etc.)