npm install fails with babel error about hazy

[slurmulon]

@gfloyd apoligies for the horrendous response time on this, I don't have a very good reason other than being way too busy and having lots of unread notifications. I will do my best to improve on that front.

Do you think it would make sense to publish the lib dir and remove the preinstall script?

The only reason I didn't do this to begin with is because I don't like checking in compiled library code that parallels my source code changes, it's simply a personal preference I've developed over time. If it makes people's lives' easier to publish lib then I'm more than happy to support it.

It looks like it's because I'm using a newer version of Babel that has an option in my .babelrc that isn't supported by Babel 5.

As of 0.1.13, Babel 6 is now used along with some syntax plugins (es2015, syntax-flow, transform-flow-strip-types). This version also includes a .babelrc file.

Do you think it would make sense to publish the lib dir and remove the preinstall script?

There are two reasons (really one, they relate to the same problem) that I'm using the preinstall script.

1. This is a remnant from a hacky package.json built around Babel 5. Babel 5 had various packaging issues but the most prominent was that it failed to install before postinstall. After a lot of searching I ended up running npm install --ignore-scripts in preinstall - pretty gross/sluggish but succinct and effective.
2. I have found, that for a reason I'm not sure of yet, that Babel 6 fails to install completely as well unless you provide npm install --ignore-scripts in preinstall. If you have suggestions on avoiding this problem (preferably without needing to publish lib) then I'm all ears!

Happy to submit a PR if you want!

Please and thank you! Hoping these issues weren't too frustrating for you, and again apologies for the extremely slow response.

[slurmulon]

As of 0.1.16, hazy no longer requires the host to compile/transclude the library on their own machine. This was mostly due to me doing whatever I could to avoid publishing output folders. After realizing that NPM actually processes your .gitignore file, I addressed the issue by creating an .npmignore that doesn't include lib.

There is no need to build on the host, therefore this exception should no longer be possible. It's definitely no longer an issue after the Babel 6 upgrade in 0.1.13