Thanks for the report, must be a bug in 2.0.0 since every asset in the bundle is expected to have a name, which given the bug is not true for images.

Using a previous version of vite-plugin-ruby should avoid the problem, though I know you are using the latest version to use scss entrypoints.

I don't have my computer until next week—I'll investigate and create a patch.

After move images folder into entrypoints, it can work and the hg.png generated twice after build

../../../public/vite/assets/hg.db495701.png            8.19kb
../../../public/vite/assets/images/hg.db495701.png     8.19kb

body {
  background: url('/images/hg.png');
}

<img src="<%= vite_asset_path 'images/hg.png' %>" />

The images folder does not play a special role at the moment–moving it to entrypoints is correct if you want to use vite_asset_path.

@ElMassimo Thanks, it seems if want use vite with rails, another way is move images folder to app/javascript folder and generate manifest file by custom codes. Vite's manifest file looks like

{
  "application.js": {
    "file": "assets/application.23f17bc7.js",
    "src": "application.js",
    "isEntry": true,
    "css": [
      "assets/application.4b2ec947.css"
    ],
    "assets": [
      "assets/hg.db495701.png"
    ]
  }
}

If the assets entry move out the application.js node, like this

{
  "application.js": {
    "file": "assets/application.23f17bc7.js",
    "src": "application.js",
    "isEntry": true,
    "css": [
      "assets/application.4b2ec947.css"
    ]
  },

 "images/hg.png": "assets/hg.db495701.png",
}

then we can use vite_asset_path('images/hg.png') in view.

I've created a PR for vite to solve the issue. vitejs/vite#3050, it also can solve custom manifest format problem.

Asset duplication because of put images in entrypoints folder, vite-plugin-ruby generates a file and vite also generates file when you use the image in stylesheet. The right way is put images to images folder, if you want to use image in rails view, you should use global import in application.js.

import.meta.globEager('../images/**/*')

I also came across this problem, Is there any workaround for this problem?
or Do I need to wait until this PR merges and releases?

I also came across this problem, Is there any workaround for this problem?
or Do I need to wait until this PR merges and releases?

I'm working on that, i'll submit a new PR to solve the two problem.

Hi folks, adding the name to asset chunks would certainly simplify the internals of this library.

In the meantime (and to provide support to users in older Vite versions), I have fixed the build manifest error when referencing other assets, as well as the duplication problem in vite-plugin-ruby@2.0.1.

Please upgrade, and let me know how it goes.

@ElMassimo It works, thanks.

I also came across this problem, Is there any workaround for this problem?
or Do I need to wait until this PR merges and releases?

ElMassimo has done the great work. At beginning, my plan is to move vite config.root to app/frontend and puts images in app/frontend/images. I found the newest version can work well with rails now. Thanks ElMassimo's great work.