Incompatible with Vite 8 Beta (i.e. vite with rolldown)

[KieranP]

Vite is going to replace their core system with rolldown in an upcoming version. They released a preview version last week, but there are issue with vite-plugin-ruby.

I filed an issue with Rolldown-vite team incase they want to investigate something on their end and thought I should mention it here as well.

vitejs/rolldown-vite#235

[sapphi-red]

I guess it's because rolldown does not support the deprecated name property.

vite_ruby/vite-plugin-ruby/src/index.ts

Lines 103 to 104 in d4bd2ef

	const outputFileName = (ext: string) => ({ name }: { name: string }) => {
	const shortName = basename(name).split('.')[0]

[zainudinsainal]

yes it seems the name property is causing the error. by adding the code below in vite.config.js file, i was able to run rails assets:precompile with rolldown-vite package.

export default defineConfig({
  build: {
    rollupOptions: {
      output: {
        assetFileNames: () => {
          return 'assets/[name]-[hash][extname]';
        },
      },
    },
  },

[gurgeous]

Thanks for the tip @zainudinsainal. I did not find this to be sufficient, at least with the latest version of rolldown. After some investigation I ended up adding a custom plugin to fix the issue. Thanks all, we love vite ruby!

//
// The purpose of this plugin is to fix the vite ruby config that doesn't work
// with rolldown. It's not enough to populate the `build:` property in
// defineConfig, because there is some confusion about rollup vs. rolldown
// options. The config below is deeply merged into the vite config, so the
// `input` property setup by vite ruby gets correctly passed through.
//
// https://github.com/ElMassimo/vite_ruby/issues/557#issuecomment-2989633811
//

const ViteRubyHack = () => {
  const output = { assetFileNames: "assets/[name]-[hash][extname]" };
  return {
    config: () => ({
      build: {
        rolldownOptions: { output },
        rollupOptions: { output },
      },
    }),
  };
};

and add it after vite ruby:

export default defineConfig({
  plugins: [
    ...
    VitePluginRuby(),
    ViteRubyHack(),
    ...

[BilalBudhani]

thanks for sharing the workaround @gurgeous, it works!

[zainudinsainal]

thanks for the update @gurgeous. Yes, the latest version of rolldown-vite has breaking changes as mentioned in this PR #571. This gem need to be updated with rolldownOptions to use with rolldown-vite.

[KieranP]

Getting this error in latest vite-rolldown, it's looking for app/frontend/index.html entrypoint, evidently vite_ruby isn't setting the vite entrypoints in a way that is compatible with vite-rolldown... It looks like the moment any config/plugin specified rolldownOptions, rollupOptions is ignored. Which means this plugins input options are wiped out.

pm vite build
10:03:04 am [vite-plugin-svelte] !!! Support for rolldown-vite in vite-plugin-svelte is experimental (rolldown: 1.0.0-beta.45, vite: 7.1.20) !!!
	See https://github.com/sveltejs/vite-plugin-svelte/issues/1143 for a list of known issues and to report feedback.
10:03:04 am [vite] warning: Both `rollupOptions` and `rolldownOptions` were specified by "vite-plugin-ruby" plugin. `rollupOptions` specified by that plugin will be ignored.
rolldown-vite v7.1.20 building for production...
✓ 0 modules transformed.
✗ Build failed in 5ms
error during build:
Build failed with 1 error:

[UNRESOLVED_ENTRY] Error: Cannot resolve entry module app/frontend/index.html.

    at aggregateBindingErrorsIntoJsError (file:///app/node_modules/.pnpm/rolldown@1.0.0-beta.45/node_modules/rolldown/dist/shared/src-CPA2meNe.mjs:2485:18)
    at unwrapBindingResult (file:///app/node_modules/.pnpm/rolldown@1.0.0-beta.45/node_modules/rolldown/dist/shared/src-CPA2meNe.mjs:2460:128)
    at RolldownBuild.write (file:///app/node_modules/.pnpm/rolldown@1.0.0-beta.45/node_modules/rolldown/dist/shared/src-CPA2meNe.mjs:4242:33)
    at async buildEnvironment (file:///app/node_modules/.pnpm/rolldown-vite@7.1.20_@types+node@24.9.2_esbuild@0.25.12_sass-embedded@1.93.3_sass@1.93.3/node_modules/rolldown-vite/dist/node/chunks/node.js:33078:64)
    at async Object.build (file:///app/node_modules/.pnpm/rolldown-vite@7.1.20_@types+node@24.9.2_esbuild@0.25.12_sass-embedded@1.93.3_sass@1.93.3/node_modules/rolldown-vite/dist/node/chunks/node.js:33481:19)
    at async Object.buildApp (file:///app/node_modules/.pnpm/rolldown-vite@7.1.20_@types+node@24.9.2_esbuild@0.25.12_sass-embedded@1.93.3_sass@1.93.3/node_modules/rolldown-vite/dist/node/chunks/node.js:33478:153)
    at async CAC.<anonymous> (file:///app/node_modules/.pnpm/rolldown-vite@7.1.20_@types+node@24.9.2_esbuild@0.25.12_sass-embedded@1.93.3_sass@1.93.3/node_modules/rolldown-vite/dist/node/cli.js:629:3)

vite.config.ts

import { defineConfig } from 'vite'
import RubyPlugin from 'vite-plugin-ruby'

const isUsingRolldown = import.meta.rolldownVersion
const optionsKey = isUsingRolldown ? 'rolldownOptions' : 'rollupOptions'

export default defineConfig({
  plugins: [...RubyPlugin()],
  build: {
    assetsInlineLimit: 0,
    reportCompressedSize: false,
    [optionsKey]: {
      output: {
        assetFileNames(chunk) {
          return 'assets/[name]-[hash].[ext]'
        },
        chunkFileNames(chunk) {
          return 'assets/[name]-[hash].js'
        },
        entryFileNames(chunk) {
          return 'assets/[name]-[hash].js'
        },
      },
    },
  },
})

config/vite.json

{
  "all": {
    "sourceCodeDir": "app/frontend",
    "watchAdditionalPaths": [],
    "skipProxy": true
  },
  "development": {
    "autoBuild": true,
    "publicOutputDir": "vite-dev",
    "port": 3036
  },
  "test": {
    "autoBuild": true,
    "publicOutputDir": "vite-test",
    "port": 3037
  }
}

[dominikklein]

Can we do something from bringing this forward? :-) I think there is also already a related PR.

[dmix]

👍 rolldown-vite will be coming out soon and it would be good to get an alpha out so we can test thing before adopting

[KieranP]

Vite 8 Beta has just been announced - https://vite.dev/blog/announcing-vite8-beta - I've updated the issues title to make it clear that vite_ruby is currently incomptaible with this new version of vite. cc @ElMassimo

[dmix]

might be good time to help test / improve this PR on real projects #571