shakapacker VS vite_ruby

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.

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).