pingcrm VS vite_ruby

Here is Demo that you will find in the Docs https://github.com/ledermann/pingcrm/

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