Compiled assets in 'lib' folder are not in the release bundles about loam HOT 2 CLOSED

Okay, this turned out to be a combination of a couple things:

• GitHub is autogenerating releases based on tags, but the lib folder is in .gitignore so it doesn't get included in the autogenerated bundles.
• I botched the alpha-8 release to NPM and then forgot to push the new alpha-9 tag so GitHub didn't pick it up.

I think for now, probably the best way to do this is for you to use npm / yarn to install locally; the NPM bundles do have the lib folder.

I've also opened an issue to add deployment functionality to Travis so that merges to master get automatically bundled and pushed up to both GitHub releases and NPM. That should avoid both botched deploys and the misleading GitHub autogenerated releases. I've also opened an issue to add installation instructions to the README; it wasn't clear that this package is available on NPM in the first place.

from loam.

I realize that even when trying to explain specifically this one thing, I still did a horrible making it clear that npm install loam will work. It does, and is probably the best way to get the compiled assets.

from loam.