Skip to content

docs: clarify accepted version prefixes - #952

Open
butrico31 wants to merge 1 commit into
npm:mainfrom
butrico31:docs/version-prefixes
Open

butrico31 wants to merge 1 commit into
npm:mainfrom
butrico31:docs/version-prefixes

Conversation

@butrico31

Copy link
Copy Markdown

The Versions section says a leading = is stripped from versions, but valid('=1.2.3') returns null by default. This was identified in #690, where the requested follow-up was to make the docs reflect the existing behavior, and raised again in #951 (Q5).

Clarify that v is accepted for compatibility, while = is a range equality operator and is accepted in a version with loose: true. Add examples that distinguish these cases.

Validation: executed all four examples against this checkout; npm test passed, including 100% coverage, ESLint, and the template-oss check.

Prepared with OpenAI Codex assistance.

@butrico31
butrico31 requested a review from a team as a code owner November 12, 2026 11:10
@ljharb

ljharb commented Nov 12, 2026

Copy link
Copy Markdown
Contributor

= is indeed a range indicator, not a version prefix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants