stimulus-use
turbo
Our great sponsors
stimulus-use | turbo | |
---|---|---|
9 | 145 | |
1,389 | 6,415 | |
2.8% | 1.6% | |
8.7 | 8.7 | |
4 days ago | 3 days ago | |
JavaScript | JavaScript | |
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.
- Autocomplete search with Hotwire (zero lines of Stimulus or other JS)
-
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.
-
Hotwire: best practices for stimulus
As you’ll see below, I am importing useClickOutside from stimulus-use, it’s a great library with small, composable helpers, I urge you to check it out!
-
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.
turbo
-
Turbo Streaming Modals in Ruby on Rails
I also recommend checking out the docs for Stimulus and Turbo to familiarise yourself with all their features and the APIs used in this series.
-
Htmx vs. React: A Complete Comparison – Semaphore
https://github.com/hotwired/turbo
- Turbo 8 has been released
-
What is JSDoc and why you may not need typescript for your next project?
Turbo 8 remove typescript without using JSDOC
-
Coming to grips with JS: a Rubyist's deep dive
Experiment using Turbo to drive front-end behavior: "Turbo 7.2.0 (currently in beta) allows you to define your own Stream actions which can be any JS code you want. By combining a custom Stream action or two with web components, you can essentially drive reactive frontend behavior from the backend stupidly easily. Loooove it! 😍 […] For a turnkey example, you could check out https://github.com/hopsoft/turbo_ready " —Jared White on The Spicy Web Discord
-
Improving a web component, one step at a time
This handles disconnection (as could be done by any destructive change to the DOM, like navigating with Turbo or htmx, I'm not even talking about using the element in a JavaScript-heavy web app) but not reconnection though, and we've exited early from the connectedCallback to avoid initializing the element twice, so this change actually broke our component in these situations where it's moved around, or stashed and then reinserted. To fix that, we need to always call addSparkles in connectedCallback, so move all the rest into an if, that's actually as simple as that… except that when the user prefers reduced motion, sparkles are never removed, so they keep piling in each time the element is connected again. One way to handle that, without introducing our housekeeping of individual timers, is to just remove all sparkles on disconnection. Either that or conditionally add them in connectedCallback if either we're initializing the element (including attaching the shadow DOM) or the user doesn't prefer reduced motion. The difference between both approaches is in whether we want the small animation when the sparkles appear (and appearing at new random locations). I went with the latter.
-
Mastering Rails Web Navigation with link_to and button_to Helpers - Part 2
If you think you have seen enough Rails magic, you are mistaken my friend. Rails have a new trick up its sleeve: Hotwire. And with the magical Turbo tool that comes with it, you can create modern, interactive web applications with minimal, or sometimes no JavaScript at all, providing users with an incredibly smooth experience.
-
Why you should choose HTMX for your next project
There is also Turbo and the frameworks who adopt them, Ruby on Rails, PHP Symphony and possibly others that solves the same issue in the same manner as HTMX. And the choice for HTMX is only a personal taste in this, but you should definitely learn about this, this is as cool as HTMX!
-
JavaScript First, Then TypeScript
Most controversially, the Turbo framework dropped TypeScript support altogether after assessing that strong typing was the culprit behind poor developer experience.
-
Rack Attack – Rails Tricks
Turbo[0] has been solving this for years. Quite the contrary, front-end frameworks have started to think "sending JSON is good, but actually sending HTML could be great!".
DHH's presentation[1] during Rails World 2023 is quite interesting in that regard, I recommend you give it a go (start around minute 16). I am actually very excited with his vision of the web.
[0] https://turbo.hotwired.dev/
What are some alternatives?
Capybara - Acceptance test framework for web applications
htmx - </> htmx - high power tools for HTML
dropzone - Dropzone is an easy to use drag'n'drop library. It supports image previews and shows nice progress bars.
Turbolinks - Turbolinks makes navigating your web application faster
hotwire-example-template - A collection of branches that transmit HTML over the wire.
hotwire-rails - Use Hotwire in your Ruby on Rails app
cuprite - Headless Chrome/Chromium driver for Capybara
inertia - Inertia.js lets you quickly build modern single-page React, Vue and Svelte apps using classic server-side routing and controllers.
cssui - A collection of interactive UI components in pure CSS
morphdom - Fast and lightweight DOM diffing/patching (no virtual DOM needed)
ferrum - Headless Chrome Ruby API
importmap-rails - Use ESM with importmap to manage modern JavaScript in Rails without transpiling or bundling.