module Jets::Bundle

def bundler_enabled?

Also check for Afterburner mode since in that mode jets is a standalone tool. 
def bundler_enabled?
  !Jets::Turbo.afterburner? && gemfile?
end

def bundler_groups 

def bundler_groups
  [:default, Jets.env.to_sym]
end

def gemfile? 

def gemfile?
  ENV['BUNDLE_GEMFILE'] || File.exist?("Gemfile")
end

def handle_error(e) 

def handle_error(e)
  puts e.message
  puts <<~EOL.color(:yellow)
    WARNING: Unable to require "bundler/setup"
    There may be something funny with your ruby and bundler setup.
    You can try upgrading bundler and rubygems:
        gem update --system
        gem install bundler
    Here are some links that may be helpful:
    * https://bundler.io/blog/2019/01/03/announcing-bundler-2.html
    * https://community.rubyonjets.com/t/jets-1-9-8-install-issue-bundler-setup-missing/185/2
    Also, running bundle exec in front of your command may remove this message.
  EOL
end

def require

project with another Gemfile, the load errors will also be rescued.
rescued gracefully. This is done in Jets::Commands::RakeTasks.load! In the case when user is in another
When the user calls jets help from outside the project folder, bundler is not used and the load errors get

user. So the rake tasks show up when calling jets help.
jets help. Instead, when the user is within the project folder, jets automatically requires bundler for the
This results in the user having to specific bundle exec in front of jets for those rake tasks to show up in

gem "webpacker", git: "https://github.com/tongueroo/webpacker.git"

webpacker that load rake tasks are specified with a git based source:
It also useful for when to loading Rake tasks in Jets::Commands::RakeTasks.load! For example, some gems like

Gemfile. This means the user will not have to explictly require dependencies.
Bundler.require called when environment boots up via Jets.boot. This will eagerly require all gems in the 
def require
  return unless bundler_enabled?
  Kernel.require "bundler/setup"
  Bundler.require(*bundler_groups)
rescue LoadError => e
  handle_error(e)
end

def setup


Later in Jets::Booter, Bundle.require is called and includes the Jets.env group.
The initially Bundler.setup does not include the Jets.env group.
Note, this is called super early right before require "zeitwerk"

The Bundler.setup is only necessary because we use Bundler.require after require "zeitwerk" is called.

Reference: https://www.justinweiss.com/articles/what-are-the-differences-between-irb/
Bundler.setup is essentially the same as `bundle exec`
This allows zeitwork module autovivification to work even if the user has not called jets with `bundle exec jets`.
Looks like for zeitwerk module autovivification to work `bundle exec` must be called. 
def setup
  return unless bundler_enabled?
  Kernel.require "bundler/setup"
  Bundler.setup # Same as Bundler.setup(:default)
rescue LoadError => e
  handle_error(e)
end