Publish beta to npm with beta tag about client-js

[vlad-ignatov]

Hi @joeldenning

The first example you posted (install from npm) installs the old version. That was simple, because it was only publishing the built files.

v2 is different, because we also publish the source (to be used in Node) and a few other stuff. We are looking for a way to optimize that...

As for the "dev" tag, we did actually publish it on NPM as fhirclient@dev, but then we quickly realized that it wasn't the best idea. The code is still changing too frequently and we can't keep it up to date on npm. For now, the most convenient way of using it seems to be the old-fashion way:

<script src="https://combinatronics.com/smart-on-fhir/client-js/master/build/fhir-client.js"></script> 

Note that this link will always point to the latest build pushed on GitHub.

[joeldenning]

Thanks for the response. I disagree that you can't publish betas, since it's well understood that betas can have breaking changes before the final release. (I do this in many of my projects - example). However, it's your project and I respect that 😄 . I appreciate the work you have put into it.