-
Notifications
You must be signed in to change notification settings - Fork 136
Open
Labels
bug: pending triageSomething doesn't seem to be working, but hasn't been verifiedSomething doesn't seem to be working, but hasn't been verified
Description
Description 📖
After a recent version of vite_ruby that explicity included a dependency on Logger 1.6 , we are now getting error on the server.
Reproduction 🐞
The error on the server is:
You have already activated logger 1.5.0, but your Gemfile requires logger 1.6.5. Since logger is a default gem, you can either remove your dependency on it or try updating to a newer version of bundler that supports logger as a default gem. (Gem::LoadError)
Vite Ruby Info
Run bin/rake vite:info and provide the output:
## On the server.
[rpant@ruby1-ol9 current]$ bin/vite info
bin/vite present?: true
vite_ruby: 3.9.1
vite_rails: 3.0.19
rails: 7.0.4.2
ruby: ruby 3.1.2p20 (2022-04-12 revision 4491bb740a) [x86_64-linux]
node: v18.20.8
pnpm: 10.5.2
## locally
rpant@MBK-WCV41P7JVM aasp % bin/vite info
bin/vite present?: true
vite_ruby: 3.9.1
vite_rails: 3.0.19
rails: 7.0.4.2
ruby: ruby 3.1.2p20 (2022-04-12 revision 4491bb740a) [x86_64-darwin21]
node: v18.20.5
pnpm: 10.5.2
Logs 📜
If not providing a reproduction:
Output
Run DEBUG=vite-plugin-ruby:* bin/vite dev or DEBUG=vite-plugin-ruby:* bin/vite build and provide the output:
There is no issue with the build and both vite dev and vite build run fine. The issue is that on the server the default logger gem is different than the one gemfile that vite ruby has in its specs.
Output of `gem list logger`
logger (1.6.5, default: 1.5.0)
This is preventing the server from starting up after deploying.
Metadata
Metadata
Assignees
Labels
bug: pending triageSomething doesn't seem to be working, but hasn't been verifiedSomething doesn't seem to be working, but hasn't been verified