puppeteer
Headless Chrome Node.js API [Moved to: https://github.com/puppeteer/puppeteer] (by GoogleChrome)
ferrum
Headless Chrome Ruby API (by rubycdp)
Our great sponsors
| puppeteer | ferrum | |
|---|---|---|
| 6 | 9 | |
| 68,518 | 1,642 | |
| - | 2.7% | |
| 9.0 | 8.5 | |
| about 3 years ago | 28 days ago | |
| TypeScript | Ruby | |
| Apache License 2.0 | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
puppeteer
Posts with mentions or reviews of puppeteer.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-01-14.
-
React with Google Chromes Puppeteer
Trying to render a react component with chrome puppeteer running on my Node.js environment I’m having following problem:
-
Puppeteer wait until page is completely loaded
I tried many options and suggestion on https://github.com/GoogleChrome/puppeteer/issues/1412
-
How to fill an input field using Puppeteer?
I'm using Puppeteer for E2E test, and I am now trying to fill an input field with the code below:
-
Running Puppeteer under Docker
Jering.Javascript.NodeJS.InvocationException: Failed to launch chrome! /app/Reports/jsreport/node_modules/puppeteer/.local-chromium/linux-609904/chrome-linux/chrome: error while loading shared libraries: libnss3.so: cannot open shared object file: No such file or directory TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md Error: Failed to launch chrome!
-
Do you really need NextJS for SSR? 🤔
🔨 Built with Puppeteer
-
Screenshoteer - Makes web screenshots and mobile emulations from the command line.
Tool based on puppeteer.
ferrum
Posts with mentions or reviews of ferrum.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-09-13.
- Generating PDFs in Rails using Grover
-
Learning Ruby Basics
What are you using for automation? There's a relatively new gem that I heard good things of, vessel: https://github.com/rubycdp/vessel . It uses ferrum under the hood, a set of Ruby bindings to Chrome/Chromium (https://github.com/rubycdp/ferrum).
-
Ruby web scraping gem that can handle JS?
I've used https://github.com/rubycdp/ferrum as driver for automated testing with capybara for which it works great. It recommends https://github.com/rubycdp/vessel as higher level abstraction for web scraping.
-
Automating Jekyll card generation with ruby’s Ferrum gem
require "Rubygems" require "Ferrum" def generate_card(browser, card, png, options={}) browser.go_to("http://localhost:4000/cards/#{card}") # see all the options here https://github.com/rubycdp/ferrum#screenshots browser.screenshot(path: "./images/cards/#{png}", full: true, # final image size is window_size x scale scale: 2) end browser = Ferrum::Browser.new(window_size: [800, 418]) # Check what cards we need to make Dir.glob("_posts/*").each do |post| post = File.basename(post, ".md") png = post + ".png" card = post + ".html" generate_card(browser, card, png) unless File.exists?("./images/cards/#{png}") end
- Best library for scraping dynamic page in Sidekiq background job (Selenium/Puppeteer/Cypress/Playwright)
- Ferrum – high-level API to control Chrome in Ruby
-
Migrating Selenium system tests to Cuprite
That is why we were happy to find out that a new ruby testing driver approach is being developed. It is called Cuprite, it runs the Ferrum library under the hood which, in turn, is an API that directly instruments the Chrome browser using the Chrome DevTools Protocol (CDP). About a week ago, we finally made a serious attempt to make our system test suite run on Cuprite, with especially two questions in our minds:
-
Web scraping with rails
I've used Ferrum for a couple small scripts in the past before.
-
My favorite Ruby gems
Ferrum
What are some alternatives?
When comparing puppeteer and ferrum you can also consider the following projects:
rendertron - A Headless Chrome rendering solution
Selenium WebDriver - A browser automation framework and ecosystem.
adblock-tester - Builder for https://adblock-tester.com and https://checkadblock.ru
cuprite - Headless Chrome/Chromium driver for Capybara
screenshoteer - Make website screenshots and mobile emulations from the command line.
Capybara - Acceptance test framework for web applications
solidarity - Solidarity is an environment checker for project dependencies across multiple machines.
puffing-billy - A rewriting web proxy for testing interactions between your browser and external sites. Works with ruby + rspec.
puphpeteer - A Puppeteer bridge for PHP, supporting the entire API.
threetwo - A good comic book curation app.
playwright-ruby-client - Playwright client for Ruby