[BUG] Numerical Versions After X-Ranges Are Ignored

[WalkerCodeRanger]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

A version range like 1.x.5 is valid and treated as equivalent to 1.x.x.

Expected Behavior

1.x.5 should either be invalid or match only versions like 1.0.5 and 1.10.5 but not versions like 1.0.0 or 1.2.3.

Steps To Reproduce

As I am not a Node developer but rather a maintainer of a semver package for C# that needs to support npm style version ranges, I am using https://semver.npmjs.com/ to test. Simply put the listed versions into it.

[ljharb]

I think it should just be invalid. a non-x specifier after an x specifier makes no sense at all.