Include a single gem in your
Gemfile to allow developers to optionally include their preferred set of development gems without cluttering the
Gemfile. Configurable globally or per-project.
Create a file named
.devpack in your project's directory, or in any parent directory:
# .devpack awesome_print byebug better_errors # Optionally specify a version: pry:0.13.1
Add Devpack to any project's
# Gemfile group :development, :test do gem 'devpack', '~> 0.3.2' end
Rebuild your bundle:
Load Devpack (if your gems are not auto-loaded as in e.g. a Rails application environment):
Devpack will attempt to load all configured gems immediately, providing feedback to stderr. All dependencies are loaded with
require after being recursively verified for compatibily with bundled gems before loading.
It is recommended to use a global configuration.
When using a per-project configuration,
.devpack files should be added to
Custom initializers can be loaded by creating a directory named
.devpack_initializers containing a set of
Initializers will be loaded in alphabetical order after all gems listed in the
.devpack configuration file have been loaded.
Initializers that fail to load (for any reason) will generate a warning.
# .devpack_initializers/pry.rb Pry.config.pager = false
If Rails is detected then files in the
.devpack_initializers directory will be loaded using the Rails
after_initialize hook (i.e. after all other frameworks have been initialized).
# .devpack_initializers/bullet.rb Bullet.enable = true
This strategy also applies to
To disable Devpack set the environment variable
DEVPACK_DISABLE to any value:
DEVPACK_DISABLE=1 bundle exec ruby myapp.rb
To see the full traceback of any errors encountered at load time set the environment variable
DEVPACK_DEBUG to any value:
DEVPACK_DEBUG=1 bundle exec ruby myapp.rb
The gem is available as open source under the terms of the MIT License.