vscode-pnpm-catalog-lens

🔗 Linked issue I saw the discuss first but I'd be fine with continuing to use my fork, if need be. Of course, I hope that you will agree that this would be a beneficial addition. 🧭 Context I was actually looking for a convenient way to upgrade dependencies that are declared through a catalog. Especially when it comes to dependencies that have 0 as the major version. Because currently, the flow is: 1. Navigate to and open the catalog. 2. Use e.g. to figure out what the latest version is. 2. Manually bump the version number. 3. Run package installation. With this contribution, it would simply be: https://github.com/user-attachments/assets/2004da29-b5c5-410e-9084-9b2edd7fc5c0 This video also illustrates why I chose to spawn a terminal instead of simply upgrading in the background. Sometimes, we get prompts. 📚 Description Added upgrade link to the markdown code in the popup. (As well as info about what version is currently actually installed and whether it's already the latest.) Added command that actually does the upgrade: Added a node_modules watcher to invalidate info about what's currently installed. A new tracked ref also gets triggered by this, so that a possibly already open package.json updates when the user runs package installation. Minor changes Fixed task waiting forever if there was already a build when starting the extension via debugger. Subjective changes Please let me know if I should revert/change this. I initially had issues with it during development, hence the adjustments. Bump pnpm (also removed it as a dev dependency, since that caused a conflict and that dependecy seems to be unused anyway) and disable due to buggy behavior.

Description Adds a hover provider that shows package description, latest version (with relative publish time), and homepage when you hover a catalog entry. Works across all three supported workspace formats: pnpm: yarn: bun: root (root-level / plus the legacy / shape) Uses pacote to fetch package metadata. Handles , scoped packages, auth tokens, and registry resolution natively. Thanks to @ikeyan for the suggestion. Linked Issues resolves #4 Additional context 1. Respects (same gate VS Code's built-in npm extension uses for hovers.) Off → no hover. 2. helper for relative date formatting is adapted from VS Code's npm extension date.ts Demo: https://github.com/user-attachments/assets/4b605690-111f-44fa-a3f5-e21517bd5354

Describe the bug When opening a inside a Bun workspace, the extension logs: I tracked this down to , and disabling the extension makes the message go away. In my case the workspace is using Bun, but there is no / yet. VS Code is also configured with . I think this case should not be treated as an error. If no is present, maybe the extension can fall back to other Bun signals, for example: in the root Bun workspace/catalog fields in the root At minimum, this log probably should not be . Reproduction 1. Create a Bun workspace with catalogs in root 2. Do not generate / 3. Open a child package 4. Check the Debug Console System Info Used Package Manager bun Validations [x] Follow our Code of Conduct [x] Read the Contributing Guide. [x] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate. [x] Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead. [x] The provided reproduction is a minimal reproducible of the bug. Contributions [x] I am willing to submit a PR to fix this issue [ ] I am willing to submit a PR with failing tests (actually just go ahead and do it, thanks!)