Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add logger as a runtime dependency rather than default gem #502

Merged
merged 2 commits into from
Oct 11, 2024

Conversation

joeldrapper
Copy link
Contributor

Description 📖

The default gem logger will be removed from Ruby 3.5.0 and must now be installed separately. This also resolves a warning in Ruby 3.3.5.

Background 📜

Ruby is removing some of the “default” gems so they now need to be installed separately.

The Fix 🔨

I’ve added the logger gem as a runtime dependency.

Screenshots 📷

I don’t have any screenshots, but I have a copy of the warning message in Ruby 3.3.5.

warning: logger was loaded from the standard library, but will no longer be part of the default gems starting from Ruby 3.5.0.

The default gem `logger` will be removed from Ruby 3.5.0 and must now be installed separately. This also resolves a warning in Ruby 3.3.5.
@@ -21,6 +21,7 @@ Gem::Specification.new do |s|
s.add_dependency 'dry-cli', '>= 0.7', '< 2'
s.add_dependency 'rack-proxy', '~> 0.6', '>= 0.6.1'
s.add_dependency 'zeitwerk', '~> 2.2'
s.add_dependency 'logger', '~> 1.6'
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don’t know if vite_ruby actually depends on ~> 1.6 or if it would be happy with an older version of the gem. It looks like 1.6.1 does support Ruby versions back to 2.5.0 so there shouldn’t be any issues there.

@ElMassimo
Copy link
Owner

Thanks!

@ElMassimo ElMassimo merged commit 6abbccf into ElMassimo:main Oct 11, 2024
17 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants