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 IDE extension recommendations for improved development tooling support.

[coderabbitai]

📝 Walkthrough

Walkthrough

The VSCode extensions recommendations configuration file was updated to replace one extension recommendation with another. The deprecated "vscode-versionlens" extension was swapped for "npm-version-lens" in the extensions array.

Changes

Cohort / File(s)	Summary
VSCode Configuration .vscode/extensions.json	Replaced extension recommendation "pflannery.vscode-versionlens" with "legalfina.npm-version-lens" in the recommendations array.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~5 minutes

Poem

🐰 Hop hop, a lens so new,
Version tracking, fresh and true!
npm-lens now leads the way,
Dependencies bright as clover day! 🌿✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: replacing one extension recommendation with npm-version-lens in the VSCode configuration file.
Description check	✅ Passed	The description provides context and motivation for the change, but does not include the 'Type of Change' section from the template.
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 7: Remove or replace the "legalfina.npm-version-lens" entry in the
extensions list because it only supports package.json; either delete that line
if version-lens functionality isn't required for this Flutter repo, or replace
it with the extension that supports pubspec.yaml (e.g.,
"pflannery.vscode-versionlens" / "Version Lens" which supports pub.dev) so
inline dependency versioning works for pubspec.yaml; update the
.vscode/extensions.json entry referencing legalfina.npm-version-lens
accordingly.

[coderabbitai]

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🌐 Web query:

npm-version-lens VS Code extension pubspec.yaml dart support

💡 Result:

npm-version-lens (or similar npm-focused “version lens” extensions) generally target Node/package.json ecosystems, not Dart.

For Dart/Flutter pubspec.yaml, the VS Code extension you want is Version Lens—it supports pub.dev and shows/upgrades dependency versions inline in pubspec.yaml. [1], [2]

Also note: the Dart-Code VS Code extension has its own improved version completion/annotations in pubspec.yaml (showing things like “latest” / “latest compatible”), so some “latest version” help may already come from Dart-Code itself depending on your SDK/editor setup. [3]

Sources: [1] [2] [3]

---

🌐 Web query:

legalfina.npm-version-lens VS Code extension documentation supported files

💡 Result:

The Legalfina “NPM Package Version Dropdown” (item Legalfina.npm-version-lens) extension currently supports only files named:

• package.json (it activates automatically when you open a package.json). [1]

Within package.json, it supports these sections:

• dependencies
• devDependencies
• peerDependencies
• optionalDependencies [1]

---

🌐 Web query:

pflannery.vscode-versionlens deprecated dart pubspec.yaml support

💡 Result:

I couldn’t find any official deprecation notice for Dart pubspec.yaml support in pflannery.vscode-versionlens.

The extension’s current VS Code Marketplace listing still explicitly lists “pub (dart)” as a supported ecosystem/language, and the project is described as active. [1] The upstream repository is hosted on GitLab under versionlens/vscode-versionlens. [2]

Sources: [1] [2]

---

🏁 Script executed:

# Check the extensions.json file to understand the project context
cat -n .vscode/extensions.json

Repository: 7span/flutter-dashing-kit

Length of output: 593

---

Remove npm-version-lens or replace with an extension that supports pubspec.yaml.

This is a Flutter project, so pubspec.yaml is the primary dependency file. The extension being replaced (pflannery.vscode-versionlens) supports Dart/pub and pubspec.yaml, while legalfina.npm-version-lens supports only package.json (npm ecosystem) and explicitly does not support pubspec.yaml. The previous extension is still active on the VS Code Marketplace and not deprecated.

This change removes version-lens functionality for the Flutter developers using this repository. If inline version management in pubspec.yaml is not needed, the extension should be removed entirely. Otherwise, keep the original extension or use the "Version Lens" extension which explicitly supports pub.dev and pubspec.yaml.

🤖 Prompt for AI Agents

In @.vscode/extensions.json at line 7, Remove or replace the
"legalfina.npm-version-lens" entry in the extensions list because it only
supports package.json; either delete that line if version-lens functionality
isn't required for this Flutter repo, or replace it with the extension that
supports pubspec.yaml (e.g., "pflannery.vscode-versionlens" / "Version Lens"
which supports pub.dev) so inline dependency versioning works for pubspec.yaml;
update the .vscode/extensions.json entry referencing legalfina.npm-version-lens
accordingly.