Rails 8

[9mm]

Hey, I'm generating a new rails 8 project after being on 7 for quite some time. It looks like there's a few large noteable changes that might affect rails_vite, like... "propshaft" as well as "thruster"

Is it OK to choose the default options? Or are those still not supported yet

[ryansch]

We're using vite with both propshaft and thruster. No issues!

[Splines]

Could someone maybe explain the relationship between Vite(-rails) and Propshaft to me? See for example the Asset pipeline Rails guide:

4. Bundle your JavaScript or CSS using a bundler

If your project requires features like dependency chaining or CSS pre-processing, you may want to consider advanced asset management alongside Propshaft.

Tools like jsbundling-rails integrates Bun, esbuild, rollup.js, or Webpack into your Rails application, while cssbundling-rails can be used to process stylesheets that use Tailwind CSS, Bootstrap, Bulma, PostCSS, or Dart Sass.

These tools complement Propshaft by handling the complex processing, while Propshaft efficiently organizes and serves the final assets.

Why would we even need Propshaft in the end if Vite is doing everything and can provide us with a bundled file? What does Propshaft have to organize in the end?

[ElMassimo]

In summary, if Vite is convenient for the type of assets you need to manage, there's no need to use propshaft.

In some projects I use propshaft for images and SVGs that are referenced from server-rendered views, in which case using Vite would not provide any advantages, while propshaft lets you use image_tag, as it's already integrated in Rails tag helpers (instead of having to use vite_image_tag, which is an option if you are referencing the same asset in your Vite bundle).

[Splines]

Wow, that was quick, thanks a lot 🎈