Kevin Ngo
Kevin Ngo
Whoops, I'll check it out. Thought I did a quick pass, but might've not got the latest build through.
I believe this issue should be constrained to memory leaks versus unit testing, linting, and Typescript.
Bumping aframe-react to latest version might help, but I recommend not using `ref`s for 3D or behavior-related logic. I'd register a component all do all the work inside there.
Try bumping aframe-react and use a component to see if it works.
Thanks, those dependencies are only used in the backend or some sub-subpackage, so it's not as severe as GitHub reports. Deprecations and renames aren't too critical either, if it works...
Thanks. It works on iOS, will have to test on Android. Let me know how the aframe.io and webvr-polyfill examples work.
OK, it seems there's an Android-related issue with the latest VREffect. I will file an issue.
Does this work now on 0.5.0?
It's been a while since activity on this lib, but I'm going to give this a shot.
You can use the animation component probably; it can animate arbitrary properties. Once it's in core, you can use it without dependencies and abstract the API more.