renovate/lib/modules/versioning/npm
Stefano Arlandini d300cd0f5c
fix(manager/composer): use `intersects()` instead of `matches()` to compare tool constraint (#34256)
Co-authored-by: Michael Kriese <michael.kriese@visualon.de>
2025-03-06 07:19:51 +00:00
..
index.spec.ts fix(manager/composer): use `intersects()` instead of `matches()` to compare tool constraint (#34256) 2025-03-06 07:19:51 +00:00
index.ts fix(manager/composer): use `intersects()` instead of `matches()` to compare tool constraint (#34256) 2025-03-06 07:19:51 +00:00
range.ts fix(versioning): bump rangeStrategy should pin if no range qualifier (#28309) 2024-04-10 09:47:14 +00:00
readme.md refactor: lib/modules (#14488) 2022-03-04 09:04:02 +01:00

readme.md

npm versioning is the most well known/widely-used implementation of Semantic Versioning 2.0.

It's important to understand that "npm" versioning scheme is not the same as "semver" versioning. SemVer's spec does not define ranges at all - so all range/constraint syntax in npm is npm-specific and not part of the spec.