SlimerJS vs Puppeteer | What are the differences? | StackShare

Puppeteer vs SlimerJS

Overview

SlimerJS

Stacks14

Followers17

Votes0

GitHub Stars3.0K

Forks256

Puppeteer

Stacks1.0K

Followers582

Votes26

Puppeteer vs SlimerJS: What are the differences?

Puppeteer: Headless Chrome Node API. 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; SlimerJS: A scriptable browser for Web developers. 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.

Puppeteer and SlimerJS can be categorized as "Headless Browsers" tools.

Puppeteer and SlimerJS are both open source tools. Puppeteer with 53.2K GitHub stars and 4.97K forks on GitHub appears to be more popular than SlimerJS with 2.87K GitHub stars and 288 GitHub forks.

🔥 Trending in Testing Frameworks on StackShare

Oglama™

Testing Frameworks

Oglama

Try it View Docs Alternatives

Try

Advice on SlimerJS, Puppeteer

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

SlimerJS	Puppeteer
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.	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.
Read and write files; Load a web page and inspect its content; Act on a web page like a user: click on links, fill in form fields etc; Listen for network events, to do network monitoring during the load of a webpage; Taking screenshots of a web page.	-
Statistics
GitHub Stars 3.0K	GitHub Stars -
GitHub Forks 256	GitHub Forks -
Stacks 14	Stacks 1.0K
Followers 17	Followers 582
Votes 0	Votes 26
Pros & Cons
No community feedback yet	Pros 10 Scriptable web browser 10 Very well documented 6 Promise based Cons 10 Chrome only
Integrations
StackStorm CasperJS bip.io Poltergeist Trails	Node.js

What are some alternatives to SlimerJS, Puppeteer?

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.

PhantomJS

PhantomJS is a headless WebKit scriptable with JavaScript. It is used by hundreds of developers and dozens of organizations for web-related development workflow.

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.

Chromeless

Chrome automation made simple. Runs locally or headless on AWS Lambda.

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.)