Error installing next_rails: zeitwerk requires Ruby version >= 2.4.4.

[fernandodrf]

Hi there, I am trying to use this gem to upgrade a rails app from 3.2 using ruby 2.3.0, but i am unable to install it. I get the following error:

❯ gem install next_rails
Fetching: colorize-0.8.1.gem (100%)
Successfully installed colorize-0.8.1
Fetching: thread_safe-0.3.6.gem (100%)
Successfully installed thread_safe-0.3.6
Fetching: tzinfo-1.2.7.gem (100%)
Successfully installed tzinfo-1.2.7
Fetching: zeitwerk-2.3.1.gem (100%)
ERROR:  Error installing next_rails:
        zeitwerk requires Ruby version >= 2.4.4.


❯ gem env
RubyGems Environment:      
  - RUBYGEMS VERSION: 2.5.1
  - RUBY VERSION: 2.3.0 (2015-12-25 patchlevel 0) [x86_64-linux]
  - INSTALLATION DIRECTORY: /usr/share/rvm/gems/ruby-2.3.0@upgrails4
  - USER INSTALLATION DIRECTORY: /home/vagrant/.gem/ruby/2.3.0
  - RUBY EXECUTABLE: /usr/share/rvm/rubies/ruby-2.3.0/bin/ruby
  - EXECUTABLE DIRECTORY: /usr/share/rvm/gems/ruby-2.3.0@upgrails4/bin
  - SPEC CACHE DIRECTORY: /home/vagrant/.gem/specs
  - SYSTEM CONFIGURATION DIRECTORY: /etc
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86_64-linux
  - GEM PATHS:
     - /usr/share/rvm/gems/ruby-2.3.0@upgrails4
     - /usr/share/rvm/gems/ruby-2.3.0@global
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :backtrace => false
     - :bulk_threshold => 1000
     - "gem" => "--no-document"
  - REMOTE SOURCES:
     - https://rubygems.org/
  - SHELL PATH:
     - /usr/share/rvm/gems/ruby-2.3.0@upgrails4/bin
     - /usr/share/rvm/gems/ruby-2.3.0@global/bin
     - /usr/share/rvm/rubies/ruby-2.3.0/bin
     - /usr/share/rvm/bin
     - /usr/local/sbin
     - /usr/local/bin
     - /usr/sbin
     - /usr/bin
     - /sbin
     - /bin
     - /usr/games
     - /usr/local/games

Any help will be appreciated, thanks!

[fernandodrf]

I upgraded to ruby 2.3.8 but I am still having problems with zeitwerk:

❯ gem install next_rails
Fetching colorize-0.8.1.gem
Fetching zeitwerk-2.3.1.gem
Fetching concurrent-ruby-1.1.6.gem
Fetching erubi-1.9.0.gem
Fetching thread_safe-0.3.6.gem
Fetching tzinfo-1.2.7.gem
Fetching mini_portile2-2.4.0.gem
Fetching crass-1.0.6.gem
Fetching activesupport-6.0.3.2.gem
Fetching builder-3.2.4.gem
Fetching rails-dom-testing-2.0.3.gem
Fetching nokogiri-1.10.10.gem
Fetching loofah-2.6.0.gem
Fetching rails-html-sanitizer-1.3.0.gem
Fetching next_rails-1.0.2.gem
Fetching i18n-1.8.3.gem
Fetching actionview-6.0.3.2.gem
Successfully installed colorize-0.8.1
Successfully installed concurrent-ruby-1.1.6

HEADS UP! i18n 1.1 changed fallbacks to exclude default locale.
But that may break your application.

If you are upgrading your Rails application from an older version of Rails:

Please check your Rails app for 'config.i18n.fallbacks = true'.
If you're using I18n (>= 1.1.0) and Rails (< 5.2.2), this should be
'config.i18n.fallbacks = [I18n.default_locale]'.
If not, fallbacks will be broken in your app by I18n 1.1.x.

If you are starting a NEW Rails application, you can ignore this notice.

For more info see:
https://github.com/svenfuchs/i18n/releases/tag/v1.1.0

Successfully installed i18n-1.8.3
Successfully installed thread_safe-0.3.6
Successfully installed tzinfo-1.2.7
ERROR:  Error installing next_rails:
        There are no versions of zeitwerk (~> 2.2, >= 2.2.2) compatible with your Ruby & RubyGems. Maybe try installing an older version of the gem you're looking for?
        zeitwerk requires Ruby version >= 2.4.4. The current ruby version is 2.3.8.459.

[manuca]

I also hit this issue and the root seems to be the dependency with actionview when it installs the latest version automatically.

When gem installs actionview it'll bring by default the latest version which depends on activesupport which depends on zeitwerk, which requires ruby >= 2.4.4.

Try installing an older version of actionview like ~> 5.2.x which doesn't depend on zeitwerk and then reinstall next_rails.

@etagwerker

[etagwerker]

@manuca @fernandodrf I believe this should be now fixed in the main branch. Could you confirm?

[fernandodrf]

@etagwerker hi, I managed to update my app without next_rails, sorry :/