Máximo Mussini

Hi Daniel! Based on the example you provided, and assuming you are configuring [`asset_host`](https://vite-ruby.netlify.app/config/#assethost) in Rails, you might want to check the build output to verify that it's not [printing...

Hi Steve! Have you tried configuring [`root`](https://vite-ruby.netlify.app/config/index.html#root)? You can use `VITE_RUBY_ROOT` to set the directory, and then adjust other paths such as [`sourceCodeDir`](https://vite-ruby.netlify.app/config/index.html#sourcecodedir) and [`publicDir`](https://vite-ruby.netlify.app/config/index.html#publicdir) to match your setup.

Hi Christophe! I think the most elegant way to fix this, is for Vitest to allow resolving reporter paths against `process.cwd()`, as a fallback. Additionally, allowing to explicitly pass a...

Hi Andrii! Seems unusual, `ViteRuby::CLI` already [requires `dry/cli`](https://github.com/ElMassimo/vite_ruby/blob/main/vite_ruby/lib/vite_ruby/cli.rb#L3). Could you provide a minimal reproduction? Out of chance, are you using the classic autoloader instead of zeitwerk?

> You can run ViteRuby::CLI from rails console to reproduce the issue That doesn't cause an error in all Rails applications, please provide a minimal reproduction.

Hi Kevin! Thanks for reporting. It seems like files in a Vite build have a different `mtime`, so the `vite:clean` task should be modified to cluster files within the time...

Closed in [824b4ef](https://github.com/ElMassimo/vite_ruby/commit/824b4ef8397828423d2ddda117bf27e365954961).

Hi @pftg and other folks! I've added support for a [`packageManager` config option](https://vite-ruby.netlify.app/config/index.html#packagemanager): - https://github.com/ElMassimo/vite_ruby/issues/324 As part of that feature, it felt it was reasonable to add experimental support for...

> Perhaps one step in the right direction would be for the installer to initialize the package.json with the right type? Agreed, happy to take a PR with that change,...

Thanks for the discussion folks, and @mattbrictson for suggesting ESM by default for new installations. This is now released in `vite_ruby-3.6.1`, no need to upgrade though. Users facing this issue...