You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had the same confusion when I was first looking at this package. I at first thought that it would make sense that new semver.Range(range, { includePrerelease: true}) included all prerelease; new semver.Range(range, { includePrerelease: false}) included no prerelease; and new semver.Range(range) included prerelease per the rules about prerelease matching.
It would be clearer if the parameter were named includeAllPrerelease. That is what I have done in my own package.
What / Why
new semver.Range
returns prerelease semver version even when includePrerelease is set to false with version 7.3.5.How
Current Behavior
Expected Behavior
range
doesn't include pre-releases whenincludePrerelease
is set to false.The text was updated successfully, but these errors were encountered: