Open oscarotero opened 2 years ago
Thanks! Potentially we should ignore the strings: rc, beta, experimental and next...
above here:
https://github.com/hayd/deno-udd/blob/19adffa05a10cc07058ae7a8b5a9e5ae49323086/mod.ts#L86-L87
I suppose the clever thing to do is if initVersion included one of those (e.g. rc) then we'd pick the latest that's matches that (also has rc) i.e. do something like versions = allowableVersions(initVersion, versions)
above this. wdyt?
(Note: the fragment handling below is a little wild... so we'd need to modify versions array.)
Yes, it makes sense. An even more clever behavior could be to sort these fragments by "stability". For example, to update from an alpha version to a beta or rc version. But I'm not sure this can work fine for all cases.
Hi. When I run udd to update my dependencies, it always update the react version to the "next" version:
I guess this is a bug because I would expect to update always to the latest stable version. The other development versions should be ignored.