Add why command

[thelovekesh]

Add why command to explain why a package exists.

Example:

$ wpm why elementor
cli (dependencies)
└─ dinopack-for-elementor@1.0.5
   └─ elementor@3.34.1

cli (dependencies)
└─ wte-elementor-widgets@1.4.9
   └─ elementor@3.34.1

[gemini-code-assist]

Summary of Changes

Hello @thelovekesh, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces a new why command to the wpm CLI, enabling users to understand the rationale behind a package's installation. By analyzing the project's wpm.json and wpm.lock files, the command constructs and displays the dependency paths leading to a specified package, offering a clear view of its role within the project's dependency graph. This enhancement improves transparency and debugging capabilities for package management.

Highlights

• New why command: Introduces a wpm why [PACKAGE] command to explain the presence of a package in the lockfile.
• Dependency Tree Visualization: Displays the full dependency chain of a specified package, showing how it is pulled into the project.
• Root Dependency Identification: Clearly distinguishes between direct project dependencies and development dependencies as the ultimate reasons for a package's inclusion.
• Orphaned Package Detection: Notifies the user if a package is found in the lockfile but has no apparent dependents, suggesting it might be orphaned.
• CLI Integration: The new command is seamlessly integrated into the existing wpm command-line interface, making it readily available to users.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[github-actions]

📦 wpm cli builds 📦

• darwin/amd64 - build
• darwin/arm64 - build
• linux/amd64 - build
• linux/arm/v6 - build
• linux/arm/v7 - build
• linux/arm64 - build
• linux/ppc64le - build
• linux/riscv64 - build
• linux/s390x - build
• windows/amd64 - build
• windows/arm64 - build

[gemini-code-assist]

Code Review

This pull request introduces a new why command, which is a great addition for dependency introspection. The implementation is mostly solid, but I've found a critical issue in the dependency path finding logic that could lead to an infinite loop with cyclic dependencies. I've also included a suggestion to improve maintainability by reducing code duplication and eliminating magic strings. Please see the detailed comments.