feat: exclude deprecated and prerelease versions from completion + add config

[nitodeco]

Resolves #25

Config option:

Default disabled:

Excludes deprecated versions completely. @9romise Do you think we need an option to show those as well?

[coderabbitai]

📝 Walkthrough

Walkthrough

Updates add a new boolean configuration npmx.completion.excludePrerelease (default: true) to exclude prerelease versions from completion suggestions. README table formatting was adjusted to include the new option. A new exported RegExp PRERELEASE_PATTERN was added to identify prerelease identifiers (alpha, beta, rc, canary). The version completion provider now skips entries where meta.deprecated is set and, when npmx.completion.excludePrerelease is true, skips versions matching PRERELEASE_PATTERN. No public APIs were removed or altered.

Possibly related PRs

• PR 18 (npmx-dev/vscode-npmx): Modifies src/providers/completion-item/version.ts to restructure iteration and add provenance/tag-based filtering of version completion items.
• PR 29 (npmx-dev/vscode-npmx): Rewrites version parsing/formatting and semver handling in src/providers/completion-item/version.ts, affecting version candidate selection.

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description check	✅ Passed	The pull request description references issue #25 and includes screenshots demonstrating the new configuration option for excluding prerelease versions.
Linked Issues check	✅ Passed	The pull request addresses issue #25 by excluding deprecated and prerelease versions from completion suggestions, implementing the core requirement to filter problematic releases.
Out of Scope Changes check	✅ Passed	All changes directly support the objective of filtering versions from completion suggestions; no out-of-scope modifications were introduced.

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

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

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

---

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

[9romise]

Wow! Excellent idea.

Excludes deprecated versions completely. @9romise Do you think we need an option to show those as well?

I think filtering out deprecated versions directly is perfectly fine. If someone requests to see them, we can always provide an option for that time — but I doubt anyone would intentionally select a deprecated version when updating, right? 🤔

[9romise]

Could we place this option under the version level? For example: npmx.completion.version.prelease.

[RYGRIT]

I appreciate the forward-thinking!

However, I feel that exposing 3 separate boolean flags just for version completion might be a bit too verbose/complex for the user.

I’d prefer a simpler Enum + Boolean pattern:

npmx.completion.version: Enum (Controls the source/strategy, e.g., "all" vs "provenance")

npmx.completion.excludePrerelease: Boolean (Independent filter)

This keeps the config clean while still covering the necessary logic. Since we're in preview, keeping the API surface small seems like a safer bet. WDYT?

[nitodeco]

npmx.completion.version: Enum (Controls the source/strategy, e.g., "all" vs "provenance")
npmx.completion.excludePrerelease: Boolean (Independent filter)

I like this, not too verbose and easy to expand

[9romise]

Ok! Then lets do this!

[nitodeco]

[coderabbitai]

Actionable comments posted: 1

[coderabbitai]

⚠️ Potential issue | 🟠 Major

Use the candidate semver when filtering prereleases.

Line 48 tests the installed version, not the candidate semver. This can wrongly skip or include suggestions.

✅ Suggested fix

-      if (config.completion.excludePrerelease && PRERELEASE_PATTERN.test(version))
+      if (config.completion.excludePrerelease && PRERELEASE_PATTERN.test(semver))
         continue