If you're experiencing that your bundle install command fails with an error message like this, rubygems.org might have issues with their ipv6 connectivity: $ bundle install Fetching source...
...index from https://rubygems.org/ Retrying fetcher due to error (2/4): Bundler::HTTPError Could not fetch specs from https://rubygems.org/ due to underlying error <timed out (https://rubygems.org/specs.4.8.gz)>
...has a doctor task that will print information about Environment: Ruby, Rubygems and Bundler versions List of Capistrano gems and whether an update is available All config variables and their...
Capistrano server config $ bundle exec cap staging doctor
I recently stumbled upon the Rails feature composed_of. One of our applications dealt with a lot of addresses and...
tl;dr: Ruby's Bundler environment is passed on to system calls, which may not be what you may want as it changes gem and binary lookup. Use Bundler.with_original...
...foo && bundle exec ruby -e "require %(rails) ; puts Rails.version" ) }' 3.2.13 If you want a completely Bundler-free environment, you can use Bundler.with_unbundled_env on modern Bundler (2.1+). If you...
...it can happen that there are several version of the same package in your bundle, although one would fulfill your conditions: "@babel/code-frame@^7.0.0": version "7.8.3" resolved "https://registry.yarnpkg.com/@babel/code-frame/-/code-frame-7.8.3.tgz#33e25903d7481181534e12ec0a25f16b6fcf419e" "@babel/code-frame...
...has been activated A gem is activated if it is either in the current bundle (Gemfile.lock), or if you have manually activated it using Kernel#gem (old-school).
When your JavaScript bundle is so massive that you cannot load it all up front, I would recommend to load large libraries from the compilers that need it.
Similar to the Webpack Bundle Analyzer, Chrome's new Lighthouse feature … … shows a visualisation of your JavaScript bundles. It's compatible with sourcemaps and is great for understanding large JavaScript...
...the structure of the productive Javascript code. Warning This will only work when your bundler emits source maps, which it may not do in production. Also you should bundle in...
Update RubyGems and Passenger Bundler requires Rubygems >= 1.3.6. Run gem update --system if you have an older version. It also is not compatible with older versions of passenger, so bring...
You don't need to change stuff that calls rake because rake is already Bundler-aware. Bundler replaces the Cucumber version hack We formerly used a hack to define...
...either remove your dependency on it or try updating to a newer version of bundler that supports some-gem as a default gem. You can solve this by setting PassengerPreloadBundler...
...passenger_preload_bundler to on. We do not enable this by default due to this statement from the developers: It won't be on by default because it can ironically...
So you're getting this failure when running bundle install on an older project: Your Gemfile.lock is corrupt. The following gems are missing from the DEPENDENCIES section: 'archive-tar-minitar...
This happens when you are using a new version of Bundler with a project that was bundled with a very old version of Bundler. For reasons unknown, the...
...you will not be able to use the maximum versions Rubygems 1.8.30 and Bundler 1.17.3 with https://rubygems.org/ anymore. This is a result of a server certificate on December 5th...
...t modify frozen object Could not verify the SSL certificate for https://rubygems.org/* Bundler::Fetcher::CertificateFailureError: Could not verify the SSL certificate for https://index.rubygems.org/versions. Error fetching data...
Since May 2011 we are cutting new gems using Bundler, which is less painful than cutting gems using Jeweler. You know a gem was cut using Bundler if you see...
...the word Bundler in a gem project's Rakefile. This is how to update a gem that was cut using Bundler: Say git pull or check out a repository from...
I had this error: > gem install bundler Successfully installed bundler-2.0.1 1 gem installed > bundle install Traceback (most recent call last): 2: from /home/henning/.rbenv/versions/2.5.1/bin/bundle:23:in ` ' 1: from /home/henning/.rbenv/versions/2.5.1/lib/ruby/2.5.0/rubygems.rb...
...activate_bin_path' /home/henning/.rbenv/versions/2.5.1/lib/ruby/2.5.0/rubygems.rb:289:in `find_spec_for_exe': can't find gem bundler (>= 0.a) with executable bundle (Gem::GemNotFoundException) The cause was that Bundler 2 requires RubyGems...
rbenv each gem update geordi Another useful example would be to bulk-update bundler or rubygems. Note that rbenv-each hasn't been updated since 2018, but it is...
...task does not work well with the command prompt for your OTP code with Bundler versions < 2.0.2. It just looks like the task is frozen: Workaround 1: Just type your...
...OTP code and hit enter, your gem is released afterwards. Workaround 2: Upgrade to Bundler >= 2.0.2.. Your supported Ruby versions for this gem must be >= 2.3. When rake release...
Bundler 2 requires at least Ruby 2.3.0 and RubyGems 2.5.0. You might get the following error when you try to install bundler for Ruby < 2.3: ERROR: Error installing bundler:
...error upgrade your project's ruby version or install the last supported version of Bundler for Ruby < 2.3: gem install bundler -v '~>1' You will also see an error if...
Siehe Gems, bundler, rbenv [1d] im Developer Curriculum...
...to marry Rails and the copied gem. This notes describes what to do. With Bundler This is super-painful. If you just copy the gem to vendor/gems, Rails will complain...
...foolib-1-2-3.gem Now that you have a working gem in vendor/gems, you need to tell Bundler about it. In your Gemfile, change the gem's line to: gem 'foolib', :path => File.join...
Recent Bundler (1.16.1) started complaining about missing dependencies in the Gemfile. This is due to a stricter handling of specifications (see attached link). The error message looks like this:
...API or the lockfile (other-gem (< 3)). Either installing with `--full-index` or running `bundle update example-gem` should fix the problem. However, bundle install --full-index did not any...
...already required in your specs. Here is some info that should help you out: Bundler actually doesn't automatically require anything. You need to call Bundler.require(:default, :your_custom_group1...
...your spec folder (like has_defaults), and you boot its environment, it should call Bundler.require for you and you don't need to require anything yourself. If your embedded app...
On recent/fresh installations of Ruby 1.8.7 you may encounter this error why calling any bundled binary (or just bundle exec): /home/arne/.rvm/gems/ruby-1.8.7-p374@global/gems/rubygems-bundler-1.4.2/lib/rubygems-bundler/noexec.rb:75:in `setup': undefined method `name' for # (NoMethodError...
...from /home/arne/.rvm/rubies/ruby-1.8.7-p374/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:29:in `map' ... Apparently, this is due to bundler (or maybe the rubygems-bundler that RVM supplies by default) no longer working on old Rails versions (it seems...
To install gems Bundler needs to be able to talk to https://api.rubygems.org. If you are behind a proxy you can use the https_proxy environment variable:
...myproxy:123 bundle install Note that if there is no https_proxy env variable, Bundler will also look for a http_proxy env variable. With Capistrano Ideally the server you...
...all vendored gems in to a temporary folder on the server and does a bundle install there. If you need to install gems from anothere Gemfile, just do it like...
BUNDLE_GEMFILE=Gemfile.something; install-gems-remotely my.server.com This script is part of our geordi gem on github. If you get a "ERROR: no tty present and no askpass program...