Skipping vite build. Fails on Rails 7 with Capistrano 3

[octave]

Using:

• vite_rails: 3.0.5
• rails: 7.0.1
• capistrano: 3.19.0

After deploying when making changes to assets, it works fine. But when deploying without making any changes to the assets then during rake assets:precompile, what happens is Skipping vite build. Watched files have not changed since the last build. But after that the assets are not linked properly and the rails app crash: ActionView::Template::Error (Vite Ruby can't find entrypoints/application.js in public/vite/manifest.json or public/vite/manifest-assets.json.

[ElMassimo]

UPDATE: Since Vite Ruby 3.1, it's now easier to configure capistrano-rails.

See the documentation.

---

Seems like a capistrano configuration problem.

The build will only be skipped if a temporary file from a previous build is found, and no files have changed since the last successful build.

Normally, if that file persists, then the public dir along with the Vite output dir would also persist.

Make sure that the public dir is not being cleared upon deployment to avoid rebuilding unnecessarily, or force a build on every deployment (less efficient).

[ElMassimo]

Maybe this should apply to non-dev environments instead of production-only?

Building assets in staging will still set the Vite build mode to production.

Linking the assets directory is appreciable to avoid building the front app again when deploying backend-only changes.

An alternative would be to copy the public dir from the previous release when creating a new one, before the assets:precompile task is run by Capistrano. That would avoid affecting assets from previous releases (safer rollbacks), and doesn't require full recompilation if frontend assets did not change.

[antoinematyja]

Mmh not sure about this.

By default, when I run RAILS_ENV=production rails vite:build, the directory is not emptied, but with RAILS_ENV=staging rails vite:build it is. I added build: { emptyOutDir: false } to my vite.config.js and it did changed the behavior with RAILS_ENV=staging.

When I run the vite:build task in staging, vite is building for staging:

% RAILS_ENV=staging rails vite:build
Building with Vite ⚡️
vite v2.8.6 building for staging...

I guess your config.mode variable gets the RAILS_ENV value too.

[ElMassimo]

Thanks for testing it, happy to take a PR to change that to emptyOutDir: isDevelopment. I'll make sure to release a fix for that next week.

[ElMassimo]

Released the fix by @antoinematyja in [email protected] 😃

[ElMassimo]

@antoinematyja Thanks for your feedback, released [email protected] which should make it easier to configure Capistrano to work well with Vite Ruby. See:

• feat: improve capistrano-rails integration by extending asset tasks #200