The Bundler 1.17 announcement includes context and a more detailed explanation of the changes in this version. This is a summary of the biggest changes. As always, a detailed list of every change is provided in the changelog.
We’ve added a new command called
remove that allows you to remove gems from the command line. Here’s a quick example:
# Gemfile source 'https://rubygems.org' gem 'rake' gem 'json'
We can now remove a gem using
$ bundle remove json Removing gems from Gemfile json was removed.
Bundler will then remove the
json gem from the Gemfile. There also is an
--install option that will run
bundle install after the gem has been removed.
We’ve added a few options that extend existing features and improve the overall user experience:
bundle addthat will add a version constraint to new gems
bundle addto skip running
bundle installwhen adding a new gem
bundle outdatedto only show outdated gems that are listed directly in the Gemfile
We’ve added new events into Bundler for plugins. Libraries are now able to perform an action before and after each gem is installed. We are excited to see plugins take advantage of these events, and enhance the user experience on top of Bundler.
Users have been asking for a feature that will allow them to specify a location for Bundler to place any files/folders that it creates or downloads,
but until now Bundler has been hardcoded to place all of its files into
To solve this issue, we’ve added some environment variables that (optionally) let you tell Bundler exactly where to put its files.
To change the directory where Bundler will store all user-level files (which is
~/.bundle by default), set
To change the directory where Bundler caches downloaded gems and gem metadata (which is
~/.bundle/cache by default), set
To change the location of the user-level configuration file (which is
~/.bundle/config by default), set
Finally, to set the location that Bundler will look for plugin files (which is
~/.bundle/plugins by default), set