bundler
Bundler Errors
Exception classes raised by Bundler, Ruby's dependency manager. Bundler errors surface during gem installation, dependency resolution, Gemfile parsing, and source fetching.
14 codes
· All codes 14 codes
- Bundler::BundlerError BundlerError Base class for all Bundler exceptions. Catching this class intercepts any Bundler-specific error.
- Bundler::GemfileError GemfileError The Gemfile contains a syntax or semantic error (e.g. an undefined method call, a missing source declaration, or an invalid group). The error message includes the offending line.
- Bundler::GemfileNotFound GemfileNotFound No Gemfile was found in the current directory or any parent directory. Run Bundler commands from the project root containing the Gemfile, or create one with `bundle init`.
- Bundler::GemNotFound GemNotFound A gem listed in the Gemfile cannot be found in any configured source. Check gem name spelling, source declarations, and network access to the gem server.
- Bundler::GemspecError GemspecError A `.gemspec` file is missing, contains a syntax error, or omits required fields such as `name`, `version`, or `summary`. Validate the gemspec with `gem build <name>.gemspec`.
- Bundler::GitError GitError Failed to clone, fetch, or checkout a `:git` gem source. Common causes include an invalid repository URL, missing SSH keys, a branch or tag that does not exist, or a network failure.
- Bundler::HTTPError HTTPError A network error occurred while fetching gem metadata or downloading gem files from a source. Check connectivity, source URLs, and any proxy or firewall configuration.
- Bundler::InstallError InstallError A gem failed to build or install. The most common cause is a native extension failing to compile due to missing system headers, libraries, or a C compiler. The error output includes the build log.
- Bundler::InvalidOption InvalidOption An unrecognized or mutually exclusive option was passed to a Bundler command. Run `bundle help <command>` to see valid options.
- Bundler::LockfileError LockfileError The Gemfile.lock is inconsistent with the Gemfile, was written by a newer Bundler version, or is corrupted. Delete the lockfile and run `bundle install` to regenerate it, or resolve the inconsistency manually.
- Bundler::PathError PathError A `:path` gem source directory does not exist, is not readable, or does not contain a valid gemspec. Verify the path is correct relative to the Gemfile and that the directory contains a `.gemspec` file.
- Bundler::ProductionError ProductionError An operation is not permitted in deployment or frozen mode. For example, `bundle install --frozen` raises this when gems are missing from the lockfile. Ensure the lockfile is committed and up to date before deploying.
- Bundler::SolveFailure SolveFailure The dependency resolver could not find an installable set of gem versions that satisfies all Gemfile requirements. The error lists conflicting dependencies. Try relaxing version constraints or running `bundle update` on the problematic gems.
- Bundler::VersionConflict VersionConflict Gem version requirements conflict; no single combination of versions satisfies all constraints in the Gemfile. The error message lists the conflicting gems and their requirements. Running `bundle update` for the specific gem or relaxing version constraints usually resolves it.