Update the SDK to export an actual ES2015 module

[jwngr]

PRs welcome!

Currently the library is exported in such a way that you can only use require('geofire') within Node.js. This means you cannot get require('geofire') or import * as GeoFire from 'geofire' to work with ES2015-compatible browsers or browser bundlers like webpack and Browserify. We should export an actual ES2015 module to support those modern use-cases.

[RedFour]

I'm been looking for how to integrate GeoFire to my Angular 2 project. My project is created using the angular-cli which uses webpack. Does this issue mean I can't import GeoFire right now?

[jwngr]

You can include it the "old-fashioned" way. That is, just include a <script> tag for the GeoFire library in your main HTML file and use the global GeoFire object that it creates.

[zelkin]

You have no other way to integrate GeoFire with webpack ? Include a js file in html, with a beautiful angular2 apps, so bad... :(

[jwngr]

<script> tags work wonderfully even in modern app development. I'll gladly review a PR which fixes this issue if you care a lot about it being fixed.

[MichaelSolati]

@firebase-ops I'm not sure if this is still an active endeavor, but I banged out this...

https://github.com/MichaelSolati/geofire-js/tree/typescript

I believe the next steps would be to implement the tests you guys have written already as well as some build tweaks (and a uglify/bundle). Regardless, I would love help on these next steps if anyone is interested.

I'd say it's probably 75% done IMHO.