On Sat, Dec 21, 2013 at 4:01 AM, Alex Kocharin <[email protected]> wrote: > 20.12.2013, 00:13, "Sam Roberts" <[email protected]>: >> I've found force republish invaluable in the last weeks when publishes >> to npmjs.org silently half-work, leaving the tarball missing from >> cloudfare. I'd prefer a build number, but like you say, its not >> respected by npm, and I'm not really happy with having to use patch >> number as a publish-retry number. > > What about using fourth number for it? Like "1.2.3-4"? If you document out > what this versioning means, it'll be fine since immutability is much more > valuable here than strict adherence to semver (which is proven to be a bad > default anyway).
Hey Alex, not sure I follow. If 1.2.3 is broken, publishing 1.2.3-4 doesn't help, semver says the "-" is a release candidate for 1.2.3. Or are you suggesting that I always publish with a "-", so all versions published look like release candidates? That I always do first publish as 1.2.3-0? I guess I could... but about half my publishes work first time, and I hope this to get better as npmjs infrastructure gets worked on. Mostly, I just want to point out that while you can do many bad things with --force, that if the version you are force installing over was NEVER INSTALLABLE FROM npmjs.org... I don't see it as so harmful. -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
