Closed gaodeng closed 3 years ago
If you can get this in with the breaking change in the next day or so I can include it with the v5.x major version bump I need to do for these unrelated breaking changes #42
According to your suggestion, the semverLt function of the semver library is now used to compare versions, which may be a breaking change, for example 1.0.01 is now an illegal version number
If you can get this in with the breaking change in the next day or so I can include it with the v5.x major version bump I need to do for these unrelated breaking changes #42
According to your suggestion, the semverLt function of the semver library is now used to compare versions, which may be a breaking change, for example 1.0.01 is now an illegal version number
Very interesting! I'm still strongly in favor of using a standard library to do the comparison, and this is the standard library for javascript, so I think it's an okay change.
I do find it ironic that your defense of the error handling change you made as non-breaking seems correct (thank you for analyzing that and responding, by the way) but then my attempt to use a standard actually is breaking (good analysis there too)
I'll re-review this but I'm sure it's fine and even with the semver compare meaning this is maybe breaking, 5.x is still queued to go, so that's fine in my opinion
Thanks!
v5.0.0 is out now, hopefully everything works :-)
If you can get this in with the breaking change in the next day or so I can include it with the v5.x major version bump I need to do for these unrelated breaking changes #42