This would be great so that the JavaScript community who doesn't use Java can easily manage the webglearth package as a dependency for their projects. The versions on npmjs would match the releases on GitHub. For practical reasons, you might like to publish the package as webglearth and include both the 1.x.x and 2.x.x versions on npmjs. It's easy to npm install webglearth@1.x.x if needed.
Since your build system is not JavaScript-based, you'd probably just put the single pre-built file in npmjs.org. But if you're curious, goog is available for Node: https://github.com/gatapia/nclosure, which means you could convert to Node's CommonJS require() syntax which would have two big benefits:
- It'll make WebGLEarth better prepared for the imminent release of ES6 Module support in browsers, so converting
require()/module.export to import/export syntax would be straight forward. Browsers will be able to load entire libraries without needing to compile them into a single file (for development only of course, though with SPDY protocol multiple module files could be transmitted in a single stream equivalent to one large file, jspm does it already).
- You'll attract more contributors since most of them are using Node.js and JavaScript-based tools to develop packages instead of Java. One language for the win. ;D
This would be great so that the JavaScript community who doesn't use Java can easily manage the webglearth package as a dependency for their projects. The versions on npmjs would match the releases on GitHub. For practical reasons, you might like to publish the package as
webglearthand include both the 1.x.x and 2.x.x versions on npmjs. It's easy tonpm install webglearth@1.x.xif needed.Since your build system is not JavaScript-based, you'd probably just put the single pre-built file in npmjs.org. But if you're curious, goog is available for Node: https://github.com/gatapia/nclosure, which means you could convert to Node's CommonJS
require()syntax which would have two big benefits:require()/module.exporttoimport/exportsyntax would be straight forward. Browsers will be able to load entire libraries without needing to compile them into a single file (for development only of course, though with SPDY protocol multiple module files could be transmitted in a single stream equivalent to one large file, jspm does it already).