stimulus_reflex VS vite_ruby

Then there are stack-specific libraries: StimulusReflex for Rails, Phoenix LiveView, Laravel Livewire, Unicorn and Tetra for Django, Blazor for .NET, … and the list goes on.

Morphing and the concept to do refreshes after broadcast are hardly new. Stimulus Reflex has employed morphing to update the page for years, and CableReady::Updatable, which allows listening to model requests for refreshes, has also been around for a while. But I am excited to see these concepts being adopted in Turbo and becoming more mainstream.

Stimulus Reflex (Ruby), which predates Hotwire, also deserves a mention, though most of its momentum seemed to stall when Hotwire was announced.

https://docs.stimulusreflex.com/

Hi there, not crazy experienced on the topic but after some research i made for personal reasons i found https://mayu.live/ whick looks interesting (and as mentioned already https://docs.stimulusreflex.com/, seems to be close to Liveview)

StimulusReflex Docs pretty easy to use and release 3.5.0 is coming soon.

However, the timing may be a little off. In some ways, it feels like the "Express" way of developing for the backend is dying. We are seeing tools that blur the line between backend and frontend, trying to unify how we develop web applications. Tools like Phoenix LiveView, StimulusReflex, Laravel Livewire, Remix, Next.js, and many others are being developed.

You can also learn Rails and StimulusReflex

Reading the article and the source code, I learned a ton of stuff, as always. In his implementation, Louis is using StimulusReflex (built on top of Stimulus) to achieve this. I was curious about several points:

Now that we know that our backend is working as it should, let’s wire up our stuff. I’m gonna skip on Stimulus Reflex setup and configuration and dive right in. You can easily follow the official setup or, if you use import-maps, follow @julianrubisch’s article on the topic. I also know that leastbad has been working on an automatic installer that detects your configuration and sets everything up for you if you care to try it before the next version of SR gets released.

With the recent release of Bun and its newfound support for Vite, coupled with Ruby on Rails 7.1 incorporating native support for Bun, developers can now enhance their web development workflow significantly. Here is the effortless process of enabling Bun for Vite Ruby, ultimately streamlining your front-end builds.

Vite, in particular, ViteRuby is a solid option. It sits between ESBuild and Webpacker, and if you're looking at Webpacker, Vite may actually be a better option for you. It is a very solid option, and I've enjoyed using Vite personally.

Yep. vite_rails (website/GitHub) is the way to go.

Use vite with https://vite-ruby.netlify.app/ if you don’t go the inertia route.

--skip-javascript is necessary for avoiding conflicts on the next steps. In case of bootstrap/foundation-sites the asset pipeline is helpful so --skip-asset-pipeline is not applied.

Vite Ruby is an umbrella project with libraries that will allow you to easily integrate Vite at your favourite Ruby framework, such as Rails or Hanami, or a plain Rack app. If you are tired of waiting for webpack to compile, this project might be for you. ​ Vite.js in Ruby ## Why Vite? 🤔 Vite does not bundle your code during development, which means the dev server is extremely fast to start, and your changes will be updated instantly thanks to HMR. This is great when adjusting styles, or tweaking behavior in JS. In production, Vite bundles your code with tree-shaking, lazy-loading, and common chunk splitting out of the box, to achieve optimal loading performance. ## Why Vite in Ruby? 🤔 Vite is great on its own, but configuring it correctly to work for a Ruby app structure requires knowledge of its internals. By following existing Rails and Rack conventions, and adding a few of its own, it becomes possible for ⠀everyone to leverage Vite and its wonderful features! If you are curious about the difference, check this Jumpstart Rails template.

Vite Rails Docs

It something that basically doesn't work properly since the birth of Rails, 15 years ago. For beginners, this is a big disappointment. You have to tweak Guard-livereload (tricky and not always working, as you mentionned), or try things like browserSync (also tricky, also not always working...) My advice so far : keep Sprockets, in order to have a nice integration with older gems. And completly remove the current js-bundling + importmaps. Instead, replace with the gem 'vite_rails' (repo here : https://github.com/ElMassimo/vite_ruby).