cmd: Organize list-modules output; add --packages flag #3925
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
One thing that I always found kinda difficult was inspecting the output of
caddy list-modulesmanually/visually.I often want to know at a glance which non-standard modules a binary contains so that I can upgrade that Caddy instance without forgetting any of the modules it uses when I create its build.
This output is much easier to scan. It lists the standard modules first, then non-standard ones separately. It even counts them. I also added a
--packagesflag so you can see what Go package the module comes from.(In the future, there should be a way to easily download the same build configuration but at the latest version, or a specified version.)