Alasdair
Alasdair
Issue # 1, nice.
Ooh, didn't see this... should have looked harder -.-. Surprised this import issue didn't get fixed for the last release... A bit more info on a reproducable use case in...
I'll try to clarify the use case I have in mind in (hopefully) simpler terms: (cc @wraithgar) ## Example "library" is being developed using prerelease versions and "library" has a...
@ljharb you're absolutely right. This is mentioned as a workaround in the PR, although I'm intentionally ignoring this when discussing the issue since we need to figure out a way...
I'm seeing this problem too - again coming from the monorepo approach and trying to solve this from a few different angles. The behaviour of extends seems to be broken...
I'd imagine that even without providing any options - includePrerelease (since it's not a range), or loose (since it's 100% valid semver), the prerelease part of the version should be...
For 0.x.y i'd treat it as 0.MAJOR.MINOR where PATCH falls under minor.
@CrazyPython I like this one. You need to resolve conflicts though :D I think it would be nicer (although a fair amount of work to get all the factors and...
@googlebot I signed it!