chore: recommend npm-version-lens extension

[farshadhemmati]

Recommend npm-version-lens

This PR updates .vscode/extensions.json to recommend npm-version-lens in place of the following extension(s):

• pflannery.vscode-versionlens

Why?

npm-version-lens provides:

• Color-coded version indicators directly in package.json
• One-click version updates via an inline dropdown
• Inlay hints showing the latest available version

It is actively maintained and lightweight.

Marketplace: https://marketplace.visualstudio.com/items?itemName=Legalfina.npm-version-lens

Summary by CodeRabbit

• Chores
  • Updated recommended VS Code extension for development environment configuration.

[coderabbitai]

📝 Walkthrough

Walkthrough

Updated the VSCode recommended extensions configuration by replacing the pflannery.vscode-versionlens extension with legalfina.npm-version-lens. This is a purely configuration-based change affecting developer environment setup only.

Changes

Cohort / File(s)	Summary
VSCode Configuration .vscode/extensions.json	Replaced versionlens extension recommendation from pflannery.vscode-versionlens to legalfina.npm-version-lens

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A lens swaps for another in the dotfiles so small,
From pflannery to legalfina, the versions won't fall,
With just one plus one minus, a change light as air,
Developer tools get better, with npm-vision to spare! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and specifically summarizes the main change: replacing one VS Code extension recommendation with another (npm-version-lens).
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In @.vscode/extensions.json:
- Line 11: The workspace recommendations replaced the widely-used extension
identifier "pflannery.vscode-versionlens" with "legalfina.npm-version-lens",
which is a downgrade in adoption and risk; revert the change by restoring
"pflannery.vscode-versionlens" in the extensions list (or add justification in a
PR comment explaining why "legalfina.npm-version-lens" should replace it),
ensuring the extensions JSON contains the trusted "pflannery.vscode-versionlens"
entry or a documented rationale for the replacement.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🌐 Web query:

legalfina.npm-version-lens VS Code extension marketplace

💡 Result:

The VS Code Marketplace listing for Legalfina.npm-version-lens is “NPM Package Version Dropdown” (publisher: Legalfina). It shows inline, color-coded npm version indicators in package.json, provides a dropdown to pick any available version, and supports Ctrl/Cmd-click to open the package on npmjs.com. (marketplace.visualstudio.com)

Citations:

• 1: https://marketplace.visualstudio.com/items?itemName=Legalfina.npm-version-lens

---

🌐 Web query:

Legalfina npm-version-lens VS Code downloads rating installation count last updated

💡 Result:

VS Code Marketplace stats (as of Feb 7, 2026)

Extension (publisher.id)	Installs (Marketplace)	Rating / reviews	Last updated
NPM Package Version Dropdown (Legalfina.npm-version-lens)	5 installs (marketplace.visualstudio.com)	(1 review) (average star rating not shown in the Marketplace HTML view we could access) (marketplace.visualstudio.com)	Marketplace “last updated” date not visible in the accessible HTML; repo shows commits on Feb 7, 2026 (github.com)
Version Lens (pflannery.vscode-versionlens)	2,348,242 installs (marketplace.visualstudio.com)	≈ 4.58★ (and 90 reviews shown on Marketplace page) (vsixhub.com)	Sep 19, 2025 (vsixhub.com)

Notes:

• The Marketplace pages clearly expose install counts for both extensions. (marketplace.visualstudio.com)
• For Version Lens, a numeric average rating and update date are available via VsixHub (mirrors Marketplace metadata). (vsixhub.com)

Citations:

• 1: https://marketplace.visualstudio.com/items?itemName=Legalfina.npm-version-lens
• 2: https://marketplace.visualstudio.com/items?itemName=Legalfina.npm-version-lens
• 3: https://github.com/Legalfina/vscode-npm-package-dropdown/commits/main/
• 4: https://marketplace.visualstudio.com/items?itemName=pflannery.vscode-versionlens
• 5: https://www.vsixhub.com/vsix/1919/?utm_source=openai
• 6: https://www.vsixhub.com/vsix/1919/?utm_source=openai
• 7: https://marketplace.visualstudio.com/items?itemName=Legalfina.npm-version-lens
• 8: https://www.vsixhub.com/vsix/1919/?utm_source=openai

---

Do not replace pflannery.vscode-versionlens with legalfina.npm-version-lens without further justification.

The new extension exists and has recent commits, but it has only 5 installs and 1 review compared to the prior extension's 2.3 million installs and 4.58★ rating (90 reviews). Recommending an untested extension with virtually no adoption to all contributors introduces significant risk. Either provide strong rationale for this downgrade or restore the prior extension.

🤖 Prompt for AI Agents

In @.vscode/extensions.json at line 11, The workspace recommendations replaced
the widely-used extension identifier "pflannery.vscode-versionlens" with
"legalfina.npm-version-lens", which is a downgrade in adoption and risk; revert
the change by restoring "pflannery.vscode-versionlens" in the extensions list
(or add justification in a PR comment explaining why
"legalfina.npm-version-lens" should replace it), ensuring the extensions JSON
contains the trusted "pflannery.vscode-versionlens" entry or a documented
rationale for the replacement.