Support Vite 7 - Failed compatibility check

[Splines]

When trying to upgrade our dependencies at MaMpf, we faced this error:

ERROR -- : Failed to check mode for Vite: vite-plugin-ruby@^5.1.0 might not be compatible with vite_ruby-3.9.3

You may disable this check if needed: https://vite-ruby.netlify.app/config/#skipcompatibilitycheck

You may upgrade both by running:

     bundle exec vite upgrade

bin/rails aborted!

This error occurs with:

• Gem: vite_ruby: 3.9.3
• Npm package: vite-plugin-ruby: 5.1.3

bundle exec vite upgrade changes the package.json from vite@^7.0.0 to vite@^6.2.6, resolving to version 6.4.1, which was released October 20, 2025. Given that Vite 8 is already in Beta, I'd love to see support for Vite 7 for the awesome vite_ruby😊 We were already using Vite 7 in production, but just faced this issue now during the update.

[Splines]

Note that we were on vite_ruby: 3.9.2 and vite-plugin-ruby: 5.1.3 beforehand, so it likely has to do with the new release vite_ruby: 3.9.3.

[Splines]

For those coming here looking for a workaround, we now pin the vite_ruby version:

# Gemfile

# for now, pin vite_ruby, see https://github.com/ElMassimo/vite_ruby/issues/592
gem "vite_ruby", "3.9.2"

In case you do this, make sure to subscribe to this issue to get notified when this is resolved.

(By the way, would also love to sponsor with a small amount, see issue #521)

[jrochkind]

Had this exact annoyance myself recently.

I'm very confused how one is suppoed to tell what version of vite-plugin-ruby goes with what... if the answer is you aren't supposed to be able to know/tell, just run vite upgrade -- it has to not downgrade my vite to 6!

[jcoyne]

Vite 8 has been released now too: https://vite.dev/blog/announcing-vite8

[jrochkind]

How about a vite upgrade --just-plugin or something?

[andriytyurnikov]

FYI #607 takes the path to Vite 8 directly (skipping Vite 7) and aligns vite-plugin-ruby ^5.2 with DEFAULT_VITE_VERSION = "^8.0.0", which main already pins. Once that lands, the compat-check failure you hit on Vite 7 is moot — vite upgrade from Vite 5/6 → Vite 8 with the new plugin range no longer trips the warning.