Skip to content

chore: recommend npm-version-lens extension #62

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
farshadhemmati wants to merge 1 commit into
base: main
Choose a base branch
from
+1 −1
Open

chore: recommend npm-version-lens extension #62

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .vscode/extensions.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@
"dart-code.flutter",
"felixangelov.bloc",
"eugeniobuffo.android-manifest-snippets",
"pflannery.vscode-versionlens",
"legalfina.npm-version-lens",
Copy link

@coderabbitai coderabbitai bot Feb 7, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ 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.

"hzgood.dart-data-class-generator",
"circlecodesolution.ccs-flutter-color",
"antoinegtr.flutter-icons",
Expand Down