Replies: 2 comments 1 reply
-
Hi Konstantin! I'm using the same plugin in my projects, with the difference that I don't configure The runtime error suggests that in build mode, the relevant files are not being It might be related to how the plugin resolves relative dirs such as import { resolve } from 'node:fs'
const composablesDir = resolve(__dirname, 'app/frontend/composables')
...
dirs: [`${composablesDir}/**'], |
Beta Was this translation helpful? Give feedback.
1 reply
-
Figured it out, needed to include ts/js files, not just vue files. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I think it used to work, but have been running with HMR working (via puma-dev proxy) for all latest development.
However, I was trying to run the app without HMR to see if it helps me get the CSS anchor polyfill working (which seems to be incompatible with HMR and vite-ruby).
However, I can't even run the app at all without the Vite dev server, as it is very unhappy about anything auto-imported:
Seeing many errors like this:
ReferenceError: computed is not defined
unplugin-auto-import config looks like this:
All works fine with the Vite dev server running.
Any ideas?
Beta Was this translation helpful? Give feedback.
All reactions