TL;DR: Bundler 2.0 will rename Gemfile to gems.rb and Gemfile.lock to gems.locked (sic). The old filenames will be supported until the release of Bundler 3.0. Some more breaking changes...
Bundler 1.4.0 (still beta) can install gems in parallel, making a run of bundle install much faster...
/home/.../ruby/gems/2.1.0/gems/bundler-1.14.3/lib/bundler/rubygems_ext.rb:45:in `full_gem_path': uninitialized constant Bundler::Plugin::API::Source (NameError) Solution: Upgrade Rubygems beyond...
Install this gem and stop using bundle exec or even Geordi's handy b. Yay...
bundle open BUNDLED_GEM will open the BUNDLED_GEM's source code in your default editor...
...causes one extra round trip per file to the server and back! This is bad! Bundle-fu throws it all up into a big package and sends it out all...
...simplicity, we arrived there because of poor community interaction on the part of the Bundler developers...
Add gem 'license_finder' to the develoment dependencies of your project and run bundle install Add spec/license_finder_spec.rb with describe 'license_finder' do describe 'action_items' do before :all do...
...package_managers = @stdout.scan(/^LicenseFinder::(\w+).*is active/).flatten expect(package_managers).to contain_exactly 'Bundler', 'Please list all expected package managers here' end it 'has no dependencies with unapproved licenses...
...the libxml2 extension source. gem 'nokogiri', force_ruby_platform: true If you are on Bundler < 2.3.18, either upgrade Bundler (if possible) or use the alternative approaches from the nokogiri docs...
All servers and developer machines at makandra are already configured using the global Bundler configuration. You need to specify that using the Bundler configuration, either globally, or locally (per...
...additional Rake tasks. Unfortunately when whenever register a runner command, it doesn't use bundle exec in the resulting crontab. This gets you errors like this: `gem_original_require': no...
...such file to load -- bundler/setup (LoadError) You can work around this by putting this on the top of your config/schedule.rb: job_type :runner, "cd :path && bundle exec rails runner -e...
...called seed in term of tests. With Cucumber you can run tests like this: bundle exec cucumber --order random features # The test outout Randomized with seed 19497
...call bundle exec cucumber --order random:19497 features now, the scenarios are run in the same order. In case you use ParallelTests it might be useful to get a final...
webpack is a very powerful asset bundler written in node.js to bundle (ES6) JavaScript modules, stylesheets, images, and other assets for consumption in browsers. Webpacker is a wrapper around webpack...
...webpacker', '~> 4.x' # check if 4.x is still current! in your Gemfile. Run bundle install Finally, run bundle exec rails webpacker:install Alternatively, you can add webpacker from the...
...gems in the Gemfile. Since all versions are saved in the Gemfile.lock, everyone running bundle install will get exactly the same versions. There are some exceptions, where you can consider...
...reason is highly recommended) You want to ensure no one upgrades a library with bundle update An drawback of this approach is, that adding new gems might also upgrade existing...
...Option 1: Run without headless You can call your tests with NO_HEADLESS=1 bundle exec cucumber to see the Chrome window for this test run. (This will not work...
...a bash alias alias nh='NO_HEADLESS=1' to shorten this command to nh bundle exec cucumber. Option 2: Remote debugging With remote debugging, you can access a Docker Chrome...
...is a feature of esbuild that can keep huge libraries out of the main bundle. How code splitting works Like Webpack esbuild lets you use the await import() function to...
...disabled by default. The code above would simply inline (copy) library.js into application.js: // Compiled bundle for application.js function require_library() { // entire code of library.js } const { fun } = await Promise.resolve().then(require...
...Run the test to ensure it works within your app. The test should fail: bundle exec rspec spec/requests/default_etag_spec.rb Fixing random CSP nonces Open config/initializers/content_security_policy.rb and change the content_security_policy...
...game over anyway. Checking successful integration The test we added earlier should now pass: bundle exec rspec spec/requests/default_etag_spec.rb To manually test ETags, open the Network tab of your DevTools. Then...
...Make sure you don't have any version constraints in your Gemfile or your bundle update won't do anything! Upgrade cucumber_priority: bundle update cucumber_priority Upgrade spreewald:
...update spreewald Upgrade cucumber_factory: bundle update cucumber_factory Upgrade parallel_tests: bundle update parallel_tests Even on the latest version, parallel_tests will print some deprecation warnings due to...
...small as possible. If you're using webpack(er), you can use the webpack-bundle-analyzer plugin to get a good overview, which of your JavaScript modules take up how...
To use it, add it via npm or yarn yarn add webpack-bundle-analyzer Then add this to your environment.js: // Uncomment this code to show statistics of bundle...
Ruby includes many standard gems that are bundled into the Ruby installation. Here is an example for the gem strscan that will be displayed as default: gem list strscan
...either remove your dependency on it or try updating to a newer version of bundler that supports strscan as a default gem. (Gem::LoadError) This is what happens: bundle install...
...The following bash aliases helped me speed up that process: alias show-next-failure="bundle exec rspec --next-failure" alias open-next-failure="show-next-failure || show-next-failure --format...
# Define an alias to run the next failure alias show-next-failure="bundle exec rspec --next-failure" # IFF there is a failure, print it to the console, then...
...load on your runners like in the following example .gitlab-ci.yml: rubocop: interruptible: true script: - 'bundle exec rubocop' rspec: interruptible: true script: - 'bundle exec rspec' Afterwards new pushes to your MR...
...the last exception that was raised in the current call stack Identify Outdated Gems bundle outdated compares the versions of all gem dependencies against the gem server Get Info About...
...count can be used like "count by": [1,2,3].count { |x| x.odd? } Parallel Bundle Install bundle install --jobs 4 Run An Older Version Of Bundler Fun fact: This TIL...
...the failing features as argument for `geordi cucumber` geordi cucumber `cat tmp/parallel_cucumber_failures.log` Without geordi bundle exec cucumber @tmp/parallel_cucumber_failures.log or # Run the `cucumber profile` command bundle exec cucumber -p rerun
...between major versions. Use the latest Gemfile snippet from the Rails LTS docs. Run bundle update This will upgrade all your gems, ignoring versions locked in Gemfile.lock. This might lead...
...to conflicting gem versions due to conflicting dependencies. You might have to update (bundle update [gem names]) the necessary gems first or find a compatible gem version(s) setup by...