Stimulus VS jsbundling-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.

Any tips on preparing to work with Wiz as an incoming intern. I heard its identical to Stimulus: https://stimulus.hotwired.dev/

use Stimulus

With Stimulus, you've got a powerful tool to take your app's interactivity up a notch. For even more awesome features and Stimulus wizardry, check out the Stimulus Documentation.

The next version of Stimulus makes it easier to access parts of the private API thanks to my pull request.

I like Stimulus, it was a bit pushed by Symfony with their ux thing.

I thought it'd be https://stimulus.hotwired.dev/ for a minute but I think that ecosystem is tied too closely with rails.

Hey HN!

For those new to Rails, Stimulus (https://stimulus.hotwired.dev/) is a way to sprinkle frontend javascript code into your Rails views.

I held off using Stimulus in my Rails apps for a long time because I didn't understand it — the data= attributes looked weird, and the connection between my Rails views and Stimulus javascript controllers was confusing.

So I decided to write the guide I wish I had when I was learning Stimulus.

Hope you enjoy it! I'm happy to answer any questions, feel free to ask any.

Thanks, Harrison

Hey /r/rails, these past few weeks, I've been working on a beginner's guide to Stimulus and I'm excited to finally share it!

I think this is more like a demo - you will not get the same features as jsbundling-rails by only following instructions in the video. For that you will need to change some other files as well. You can find out what files to be added/changed from the install script. The important bits are mostly the same as in the video, but some supplement parts are not mentioned in the video. Some people actually reported in the comment that they can't deploy such app, but I think it depends.

I'm sorry, I didn't see that in your title. Using esbuild is 100% supported by Rails through this gem https://github.com/rails/jsbundling-rails. Have a look at the docs there to make sure that you're setup correctly.

Rails applications are bundler-agnostic. They do not care how you bundle your javascript code. It just expects whatever comes from the bundler to be placed under app/assets, so the asset pipeline processes it. We can see this in the official jsbundling-rails gem, which consists of scripts to install different bundlers and configure a default npm build command to generate our bundles—no interaction whatsoever with the Rails configuration. This black-box bundler logic allows us to change and update our bundler system without tuning any other aspect of our Rails application.

Hello, this is my first time setting up a rails app that also uses react, I am using https://github.com/rails/jsbundling-rails I went with esbuild because I am following this tutorial on setting it up https://www.youtube.com/watch?v=yoLJXjEV2nM, however when I run bin/dev in the terminal I get the error bin/dev: 8: exec: foreman: not found

You first install your asset handlers as you need them for your project. They can be anything from rails/jsbundling-rails and rails/tailwindcss-rails to webpacker or something custom.

The functionality comes from https://github.com/rails/jsbundling-rails and https://github.com/rails/cssbundling-rails -- both come with Rails 7 and all you have to do is generate your app with the choices you want such as -j esbuild --css tailwind.

The Rails https://github.com/rails/jsbundling-rails gem lets you pick between esbuild, rollup and Webpack. If Turbopack ends up being popular then jsbundling should be able to support it.

The nice thing about Rails now is there's no direct integration like Webpacker once was. Now we can basically use the JS tool straight up and Rails will just look at assets in a specific directory, it doesn't matter what tool generated it.