vite_javascript_tag can't find entrypoint when file is inside a Rails engine

[Eth3rnit3]

Hello Team!

I'm trying to use vite_rails in a Rails 8 app that hosts multiple Rails engines (monorepo style).
Each engine may provide its own JavaScript entrypoints.

After a fresh install of vite_rails, I configured vite.json to watch entrypoints inside engines/**/app/javascript/entrypoints/**/*.

Here is my vite.json:

{
  "all": {
    "sourceCodeDir": "app/javascript",
    "watchAdditionalPaths": [
      "engines/**/app/javascript/entrypoints/**/*"
    ],
    "additionalEntrypoints": [
      "engines/**/app/javascript/entrypoints/**/*"
    ]
  },
  "development": {
    "autoBuild": true,
    "publicOutputDir": "vite-dev",
    "port": 3036
  },
  "test": {
    "autoBuild": true,
    "publicOutputDir": "vite-test",
    "port": 3037
  }
}

My engine has an entrypoint file at:

engines/workflows/app/javascript/entrypoints/workflows.js

In the engine layout I try to load it:

<%= vite_javascript_tag 'workflows' %>

---

Expected behavior

I expected vite_rails to resolve workflows.js and include it in the layout (just like application.js from the main app).

---

Actual behavior

Vite builds the file, but the manifest key looks like this:

{
  "../../engines/workflows/app/javascript/entrypoints/workflows.js": {
    "file": "assets/workflows-D1p6yxa-.js",
    "name": "engines/workflows/app/javascript/entrypoints/workflows.js",
    "src": "../../engines/workflows/app/javascript/entrypoints/workflows.js",
    "isEntry": true
  }
}

When I call <%= vite_javascript_tag 'workflows' %>, I get:

Vite Ruby can't find entrypoints/workflows.js in the manifests.

So it seems vite_rails doesn't normalize the manifest keys when entrypoints are outside sourceCodeDir.

---

Environment

• Rails 8.0.0
• vite_rails 3.9.2
• Ruby 3.x
• Engines located under /engines/*/app/javascript/entrypoints

---

Notes

• If I move workflows.js into the main app/javascript/entrypoints, it works as expected.
• But we want each engine to keep its own JS entrypoints (engines/workflows, engines/documents, etc.).
• The file is built by Vite, but vite_rails can’t find it due to the manifest key.

---

Question

Is this a bug or a configuration issue?
Should additionalEntrypoints strip the engine path prefix so we can reference the entrypoint by its basename (like workflows)?

Or should we instead reference it with the full path (engines/workflows/app/javascript/entrypoints/workflows.js) in vite_javascript_tag?

Thanks a lot for your help!