Ian Purvis

Automated releases to npm would be very cool! We recently added CI via GitHub workflows... check out the config at [`.github/workflows/continuous.yml`](https://github.com/kripken/ammo.js/blob/master/.github/workflows/continuous.yml). If you make changes to that file in a...

Also cool... I have gotten in the habit of using semantic PR names, though I don't always do it at the commit level. This [bot](https://probot.github.io/apps/semantic-pull-requests/) is handy. @moreirayokoyama @Symbitic Maybe...

@lorenzorutayisire Fyi, some work for this was started in #322. Unfortunately we discovered performance issues with newer bullet that became a blocker. There was a potential fix identified for the...

Looks like CI is breaking because of deprecated code in https://github.com/mymindstorm/setup-emsdk. I'll work on getting this fixed later today... thanks!

@regnaio Sorry for the delay... CI is now fixed in #353. Can you rebase or merge ammo.js master into your PR branch? Thanks!

@kripken This was a quite a journey... per your recommendation in #322, I started working with the existing Bullet 2.82 benchmarks. They were not hard to get running in ammo...

I tried to keep emscripten targets in the top level CMakeLists.txt (not sure if that's the best approach, tho). So `builds/bammo.js` and `builds/bammo.wasm.js` are automatically built when you build all....

Upstream PR here: bulletphysics/bullet3#3074

> I think the bammo target in CMakeLists sets the size of memory, so why is this needed? Ah- no good reason, just avoiding the change to the CMakeLists... shall...

@kripken I wanted to preserve some flexibility in the repo history, so I walked all of bullet's tagged releases and squashed them into individual commits. So we just have to...