stimulus-rails VS turbo-rails

https://github.com/hotwired/stimulus-rails I think you need to understand how rails works because it clearly says I’m right here buddy

So I've been following the setup for https://github.com/hotwired/stimulus-rails with using the importmap, tried to get @hotwired/stimulus-loading pinned and its stating that it no longer exists...

Thanks! Now I learn 'named export' keyword... Could your show the code of named export? I searched but I don't find the one. I thinks this issue is what you say but I don't get it.

- [stimulus-rails](https://github.com/hotwired/stimulus-rails)

stimulus-rails

The tricky part of recreating the disable behavior is getting the interface to be as clean as the original. I actually opened a PR regarding a disable controller earlier this year, and the man himself said as much about the interface (I embarrassingly left the PR stale after getting swept up in my last semester of college).

The Stimulus Handbook

Have you checked out the stimulus-rails gem? It sounds like it will let you stop manually registering controllers, and use the normal ES6 import syntax for inheritance:

Run `hotwire:install Hotwire also has the following resources available: Hotwired Turbo Rails Hotwired Stimulus-rails

There's an open issue about it: https://github.com/hotwired/stimulus-rails/issues/15

The install notes here link to an issue specific to webpacker. Try that and see if it works?

True, in theory it is. A lot of it is coded in libraries like turbo-rails, though. And these are Rails-specific. But I've seen it being used in some Laravel projects, also I used it with Hanami.

Check out https://github.com/hotwired/turbo-rails/blob/main/app/models/turbo/streams/tag_builder.rb

So apart from the pretty obvious question of "why on earth would you want to do this?", I think there's a misunderstanding here of the intended use case of turbo streams. You have a page, and then some state changes on the server and you want to update the page to reflect that. Incrementing a variable doesn't really qualify as a state change, but perhaps a Product changing from "not good" to "good" would be an event worth broadcasting, which you could do using the Broadcastable concern in turbo-rails.

Use this too: https://github.com/hotwired/turbo-rails

Not mentioned in the article, but it's nice that turbo-rails recently gained the ability to pass ViewComponent objects directly to turbo stream helpers. https://github.com/hotwired/turbo-rails/pull/433

Release notes: https://github.com/hotwired/turbo-rails/releases/tag/v1.4.0

turbo/streams_channel.rb - a way to link a turbo stream with an ActionCable channel.

The readme seems to give a pretty good overview of turbo: https://github.com/hotwired/turbo-rails