Hi. I’m the as-core author. For historic reasons I’ve never made a npm bundle. Thanks to Simon showing us Observable and getting us started, I’ll start making it more more, er, observable.
Here’s the plan:
- Initially work on moving as-core to npm. I’ve never done it.
- Figure out why UMD is preferred over es6 modules
- Get hints on best practices.
- Used scoped/org npm packages
- Change repo names to something more sensible.
The group I work with, Redfish/SimTable (http://www.simtable.com/), would prefer “scoped” npm packages to avoid the name clash issues. But does that work with Observable’s require()? Indeed, the whole Observable import is a bit of a mystery. But Mike responded to a question that got me on the air, so to speak.
To give you a glimpse of noob’s issues: I’ve spent a lot of time being hyper modern: es6 modules, all repos having a github page for being a CDN, etc.
But then I find es6 modules are not first class in notebooks! I.e. es6 module import syntax doesn’t work, you have to use Observable primitives like “import” as a function.
And the CDN gh-pages really are inferior to npm. Hard to grok, given that the repos are mainly browser.
So in a bit, we’ll be on npm. First as-core, then asx. It’s kinda too bad Three.js and their examples/ fight, but thren
gave a lot of help. For asx, I’ll likely have to make some major changes.
Lastly, I’ve had several PRs to make my repos work on windows. I’m getting there but I was surprised just how big an issue that is in the node world. But, heck, node chops are a Good Thing … as is shelljs and shx.