stimulus-use
ferrum
Our great sponsors
stimulus-use | ferrum | |
---|---|---|
9 | 9 | |
1,374 | 1,628 | |
3.5% | 3.7% | |
8.7 | 8.5 | |
3 days ago | 6 days ago | |
JavaScript | Ruby | |
MIT License | MIT License |
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.
stimulus-use
-
A powerful search feature with what Rails provides out of the box
You can see that I added a dependency here: stimulus-use.
-
Discover Symfony UX’s Twig Components. UI without JS or BS.
“stimulus-use: Add composable behaviors to your Stimulus controllers, like debouncing, detecting outside clicks and many other things.
-
RVTWS: a Ruby stack for modern web apps
Actually, Stimulus is pretty cool because you can compose multiple pre-built behaviors into one Stimulus controller, for a sort of functional approach to component behaviors. The tradeoff is that a growing web of Stimulus controllers (plus HTML data attributes associated with them) can become complex and hard to understand.
-
Tailwind style CSS transitions with StimulusJS
The stimulus-use project is a collection of reusable behaviors for Stimulus. If you are familiar with React, this project is similar to React’s hooks system, but for Stimulus controllers.
-
Pagination and infinite scrolling with Rails and the Hotwire stack
To make using the IntersectionObserver API easier, we will add the wonderful stimulus-use package to our application. This is not a requirement, but it does simplify the code a bit.
-
Upgrade to Stimulus 3, say bye to IE11, and celebrate 🎉
Finally, as we recently added the Stimulus-Use library to our project, we made sure to upgrade it to current beta which supports Stimulus 3.
-
Migrating Selenium system tests to Cuprite
For example, we have a few ”live search“ fields, backed by back-end Fetch requests, on some pages. The live search function was usually triggered by the keyup event and Cuprite was such a fast typewriter that it frequently sent multiple requests almost at once. If some of the responses got a bit late or out of sync, the front-end JavaScript code began hitting issues. We solved this by adopting a technique called debouncing and, frankly, we should have done this since the beginning. By the way, we used the useDebounce module from the marvelous Stimulus-use library to achieve this.
ferrum
-
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)
-
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?
Capybara - Acceptance test framework for web applications
Selenium WebDriver - A browser automation framework and ecosystem.
cuprite - Headless Chrome/Chromium driver for Capybara
dropzone - Dropzone is an easy to use drag'n'drop library. It supports image previews and shows nice progress bars.
puppeteer - Headless Chrome Node.js API [Moved to: https://github.com/puppeteer/puppeteer]
puffing-billy - A rewriting web proxy for testing interactions between your browser and external sites. Works with ruby + rspec.
hotwire-example-template - A collection of branches that transmit HTML over the wire.
puphpeteer - A Puppeteer bridge for PHP, supporting the entire API.
Nokogiri - Nokogiri (鋸) makes it easy and painless to work with XML and HTML from Ruby.
ungoogled-chromium-fedora - RPM build for ungoogled-chromium