You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
bundler viz requires the gems to be be installed, even if there is a Gemfile.lock (e.g from bundle lock).
From my point of view, the lock file contains all the necessary information for generating the graph. Therefore I do not see the need for the gems to be actually installed.
As for my use case:
I want to generate the dependency graph of my gems in my a generic CI pipeline. The need for actually installing the gems would e.g. require the resolution of additional dependencies for native extensions inside the CI. I deem this unnecessary overhead.
Describe the problem as clearly as you can
bundler viz
requires the gems to be be installed, even if there is aGemfile.lock
(e.g frombundle lock
).From my point of view, the lock file contains all the necessary information for generating the graph. Therefore I do not see the need for the gems to be actually installed.
As for my use case:
I want to generate the dependency graph of my gems in my a generic CI pipeline. The need for actually installing the gems would e.g. require the resolution of additional dependencies for native extensions inside the CI. I deem this unnecessary overhead.
related to rubygems/bundler#1471
related to rubygems/rubygems#3342
Both mention what this issue is about, but for a different reason.
Which command did you run?
bundle viz
What were you expecting to happen?
Generate dependency graph from
Gemfile.lock
alone.What actually happened?
bundle viz
required the gems to be installed.If not included with the output of your command, run
bundle env
and paste the output belowThe text was updated successfully, but these errors were encountered: