Update published rebound.js on npm #33
Comments
Thanks! I published 0.0.3 with the current version. I've also been thinking about putting this into its own repo. I do like the idea of keeping the APIs for the Java version and the JavaScript version pretty close, but getting more iteration on the JS version might lead to some ideas for improvement in the Java version also. |
Keeping the APIs in step makes sense. Not sure having the js in it's own repo would hinder that much. I am starting to build up some helper functions around rebound.js now and it would be ideal to only pull down the few files via npm instead of the whole shebang. ;) |
Yep I'm going to create a separate repo for this. Looking forward to seeing your ideas. |
🤘 On Friday, July 25, 2014, Will Bailey notifications@github.com wrote:
Kristofer |
This is available now. What do you think about making this available on bower? I was going to do that previously but bower doesn't like projects that aren't at the root of a git repo. This should be much easier to setup now. |
Awesome! |
Do you have a preferred way of pulling this into a web project and packaging it with commonjs? I've been working on Android more lately, so I'm not up to speed on what the latest and greatest workflows look like. |
I use npm with Browserify |
The version of rebound.js on npm has an outdated version of createSpring:
Instead of what is in the docs
When following the example in the docs it throws an error since this._springConfig is never defined in the old version. *Great addition btw
I would love to see rebound.js become it's own project with it's own repo etc. I have some performance improvements to add :)
The text was updated successfully, but these errors were encountered: