The ability to reply to discussions is limited to PRO members. Want to join in the discussion? Click here to subscribe now.

Publishing a beta version

Publishing a beta version

3:37
Sometimes you're not quite ready to release a full on version of your open source library to npm. In this lesson, learn how to publish a beta version so people can try it out without tampering with anyone else using your library.
Watch this lesson now
Avatar
egghead.io

Sometimes you're not quite ready to release a full on version of your open source library to npm. In this lesson, learn how to publish a beta version so people can try it out without tampering with anyone else using your library.

Avatar
Nils

What is the general approach if you have beta running say 1.4.0-beta.0 and then someone else in the team finish another feature and want to bump the stable version 1.3.0 to 1.4.0 ?

In reply to egghead.io
Avatar
Kent C.

There are a few approaches to this. Most of the time, my beta releases are short lived. I recommend this in general. So you could add this new feature to the beta and hopefully it would be released officially soon.

If you want to have the new feature, but keep the beta version, then you may consider putting your beta versions in a separate branch, then when there's a new regular version, simply rebase the new feature in your branch, and release a beta version of the latest version.

So, in your example, you'd rebase the new feature, then release a 1.5.0-beta.0

But you have quite a bit of flexibility to do things how you want. AFAIK, there is no "standard" or "accepted" way to do this.

In reply to Nils
HEY, QUICK QUESTION!
Joel's Head
Why are we asking?