I think it would be a good idea to add AEQuery to npm. I got a project where I would like to add AEQuery as a dependency, and that would be best handled through npm.
I was thinking that we could create an npm org, but what should that be called? "aequery", "motiondesign", "aenhancers"? @Zack Lovatt and @Remco Janssen mentioned moving the project to GitHub, but there is already a user there called "motiondesign", so that would't work there.
Also, if aeq-ui is still going to be included as a different file, it should probably be published as its own package, and then probably be in it's own repository. But I think there should be some discussion about why it's included as its own file as I don't really think it need to be.
Anyone got any thoughts on this?