shakapacker VS jsbundling-rails

The migration guide https://github.com/shakacode/shakapacker/blob/master/docs/v6_upgrade.md looks like it's not too much work, I'll look into it. Still, I'd be interested about the security risks from using vulnerable packages for asset compilation.

For those of us who liked Webpacker: https://github.com/shakacode/shakapacker

There is an option to use Shakapacker

and finally to help your case as well: I would take one more step and replace webpacker with shakapacker. unfortunately in rails 7 the default js / css bundling is not based on webpack and they stopped supporting the original webpacker gem. shakapacker is a maintained successor to the webpacker gem with a better approach: they don't want to force you into writing yaml configs for something that wasn't meant to be a yaml file. also, it has way better defaults than webpacker used to have. then as soon as you got access to the real webpack configs, it'll be more clear where to look or what you need to add to the project.

webpacker -  Note that Webpacker has been retired, and it is not recommended for use unless you want the additional overhead and pain ;) That said, the folks over at ShakaCode are maintaining a fork named shakapacker

You should consider if you want to use Shakapacker (https://github.com/shakacode/shakapacker) for more JS intensive applications, or stick to the asset pipeline of jsbundling-rails. You can compare here: https://github.com/rails/jsbundling-rails/blob/main/docs/comparison_with_webpacker.md

and https://github.com/shakacode/shakapacker/pull/29

Here's the official fork: https://github.com/shakacode/shakapacker.

You can see an example of migration in this PR: https://github.com/shakacode/react_on_rails_tutorial_with_ss....

Thoughts?

Hey everybody, it's me Justin Gordon! I'm the maintainer of Shakapacker, the official successor to the "officially retired" Webpacker. The internal naming of Shakapacker is still webpacker. Upgrading is easy. You can see a comparison of the "new" jsbundling-rails with webpacker here: https://github.com/rails/jsbundling-rails/blob/main/docs/comparison_with_webpacker.md. Besides the many awesome improvements in v6 (almost all done as "Webpacker"), we've got an open PR to support SWC: https://github.com/shakacode/shakapacker/pull/29.

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.