uninitialized constant Bundler about rubocop HOT 4 CLOSED

@bbatsov I'm sorry. #12847 was not sufficiently fixed. I've opened #12849 to resolve this error.

from rubocop.

@koic @amomchilov This issue refuses to go away! 😅

from rubocop.

Thanks for the quick turn around on a PR.

May I ask why this route was chosen instead of putting in the code to require bundler?
It seems to me that if you have the bundler gem installed, it should use that to parse the lockfile. If I understand the code correctly, it will only check the lockfile if called from bundle exec. This means rubocop quietly behaves differently in the two different environments, which would be very surprising to users.

from rubocop.

Exactly, but the existence of Gemfile.lock and running via Bundler with bundle exec should be considered separately. In other words, if bundle exec is not used, it is not expected to run through Bundler. I don't see any use cases where this difference in behavior could lead to issues.

from rubocop.