@mjgardner If you want to publish a pre-release version to npm, it's simple. Just use a pre-release version (in accordance with the definition of Semantic Versioning, e.g., 1.2.3-dev.123) and tag it with anything other than latest (you can specify a tag with npm publish --tag option).
@mjgardner Oh, right, the pre-release I'm talking about is a pre-release as defined by Semantic Versioning, which means it's not guaranteed to be stable.
@mjgardner I don't think so, because revealing that a version is unstable by notation is not a bad idea for many users, it just might not be what you need.
@clacke@hongminhee Nope. My point was that the term was inaccurate, and we already have better ones in the context of software development and elsewhere. “Pre-release” typically implies availability to a limited audience.
And don’t lecture me about “most software people.” I’ve been doing this longer than either of you.
Add comment