Consider an audit of development gems
I personally find no use to most of the gems in the :development
group, and several of the ones in the :development, :test
.
It sounds like it's not understood from a team perspective which people are using which gems either, so there should be a team discussion about them and potentially a cleanup of those that don't seem useful to the current team at large.
Here's the list of ones I personally use.
group :development do
gem 'letter_opener_web', '~> 1.3.4'
gem 'listen', '>= 3.0.5', '< 3.2'
# removes:
# gem 'binding_of_caller', '~> 0.8.0'
# gem 'rails_layout', '~> 1.0.42'
# gem 'spring'
# gem 'spring-commands-rspec'
# gem 'spring-watcher-listen', '~> 2.0.0'
# gem 'web-console', '>= 3.7.0'
end
group :development, :test do
gem 'awesome_print'
gem 'factory_bot_rails'
gem 'ffaker', '~> 2.13.0'
gem 'foreman', '~> 0.86.0', require: false
gem 'rspec-parameterized', require: false
gem 'rspec-rails', '~> 3.8.2'
gem 'rubocop', '~> 0.82.0', require: false
gem 'rubocop-rspec', '~> 1.37.0', require: false
gem 'timecop', require: false
# removes:
# gem 'gitlab-styles', '~> 4.3.0', require: false
# gem 'pry-byebug', '~> 3.7.0'
# gem 'pry-rails', '~> 0.3.9'
# gem 'pry-rescue', '~> 1.5.0'
# special mention:
# this is a good gem, but we're not really utilizing it effectively as far as I can tell.
gem 'test-prof', '~> 0.10.0'
end
The following discussion from !1916 should be addressed:
-
@cwiesner started a discussion: (+5 comments) question: I have a faint memory of this being adding along with the
better_errors
gem🤔 So after checking that gem and thebetter_errors
gem the installation of the latter adds it. So maybe we should remove it as well if it's not used in another context (which I'm not aware of at this moment). What do you think?