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 developer tool recommendations for the project environment.

[coderabbitai]

📝 Walkthrough

Walkthrough

The VSCode extensions configuration is updated to replace one npm version lens extension recommendation with another, switching from "pflannery.vscode-versionlens" to "legalfina.npm-version-lens" in the .vscode/extensions.json file.

Changes

Cohort / File(s)	Summary
VSCode Configuration .vscode/extensions.json	Extension recommendation updated: replaced "pflannery.vscode-versionlens" with "legalfina.npm-version-lens" for npm version tracking.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~1 minute

Poem

🐰 A lens so fresh, a tool renewed,
From versionlens old to npm imbued,
The VSCode heart beats true and bright,
With legalfina's sharpened sight! ✨

🚥 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 'chore: recommend npm-version-lens extension' directly and clearly summarizes the main change in the pull request, which is replacing one VSCode extension recommendation with 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 recommended extension "legalfina.npm-version-lens" in
.vscode/extensions.json is an unproven alternative; either replace it with the
established extension ID "pflannery.vscode-versionlens" or add a comment and
documentation proving why "legalfina.npm-version-lens" is preferable; update the
extensions.json entry accordingly (swap the string "legalfina.npm-version-lens"
to "pflannery.vscode-versionlens" if reverting) or include a short justification
in the repo docs and PR description demonstrating clear advantages before
keeping the new ID.

[coderabbitai]

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🌐 Web query:

legalfina.npm-version-lens vscode extension marketplace

💡 Result:

The VS Code Marketplace listing for Legalfina’s “npm-version-lens” extension is:

• Name: NPM Package Version Dropdown
• Marketplace ID (itemName): Legalfina.npm-version-lens
• Link: https://marketplace.visualstudio.com/items?itemName=Legalfina.npm-version-lens
• What it does: Shows outdated npm packages in package.json with color-coded indicators and lets you pick any version from an in-editor dropdown. Requires VS Code 1.85.0+. [1]

Install in VS Code: open Quick Open (Ctrl+P) and run:
ext install Legalfina.npm-version-lens [1]

---

🌐 Web query:

Legalfina npm-version-lens install count downloads active maintained reviews

💡 Result:

Legalfina “npm-version-lens” (VS Code extension: NPM Package Version Dropdown)

• Install count: 5 installs (Visual Studio Marketplace). [1]
• Downloads: The Marketplace page shown publicly lists installs, not download totals; no separate public download count was visible from the available sources. [1]
• Activity / maintenance signals (GitHub):
  • Public repo: Legalfina/vscode-npm-package-dropdown (open source). [2]
  • Stars / forks: 3 stars, 0 forks. [2]
  • Commits / contributors: 38 commits, 2 contributors. [2]
  • Issues / PRs: 0 issues, 0 pull requests (at time of capture). [2]
• Reviews / ratings: Marketplace shows (1) rating/review count (the page does not expose the written review content in the captured view). [1]

Sources:
[1] Visual Studio Marketplace listing for Legalfina.npm-version-lens (NPM Package Version Dropdown)
[2] GitHub repo Legalfina/vscode-npm-package-dropdown

---

Don't replace Version Lens with an unproven alternative.

pflannery.vscode-versionlens (Version Lens) has hundreds of thousands of installs and is a battle-tested, mature extension. The replacement legalfina.npm-version-lens exists on the Marketplace but has only 5 installs, 3 GitHub stars, 0 forks, and 1 review—essentially an unproven alternative with minimal community validation. Before recommending this to all contributors, either demonstrate that it provides clear advantages over Version Lens or revert to the established extension.

🤖 Prompt for AI Agents

In @.vscode/extensions.json at line 11, The recommended extension
"legalfina.npm-version-lens" in .vscode/extensions.json is an unproven
alternative; either replace it with the established extension ID
"pflannery.vscode-versionlens" or add a comment and documentation proving why
"legalfina.npm-version-lens" is preferable; update the extensions.json entry
accordingly (swap the string "legalfina.npm-version-lens" to
"pflannery.vscode-versionlens" if reverting) or include a short justification in
the repo docs and PR description demonstrating clear advantages before keeping
the new ID.