kev zettler
kev zettler
This may have been fixed with #70 and #82
The vehicle demo at: http://lo-th.github.io/Oimo.js/examples/test_vehicle.html is bugged. You have to click the `demo` button in the top left to reset. Then you can use the up and down arrow keys...
even without having dynamic queue creation its just a pain in the ass to configure and maintain the index.json. If developers add or remove queues to our application we need...
This should definitely be a config value or something
I've looked into this a bit. Leaving some links: https://groups.google.com/g/discuss-webrtc/c/s6-f6OtU4wM/m/b8FEQmjTCQAJ building chromium for arm macs: https://chromium.googlesource.com/chromium/src/+/master/docs/mac_arm64.md#building-on-arm-macs
@waah42 I was able to build successfully but wasn't able to test or verify the build.
@taylorjdawson I left the links. Thats what I followed. That was months ago and have lost memory and further context. I imagine the chromium codebase has continued developing as well....
@markandrus might be a `yarn` specific problem *npm* ``` $ docker run node:9 npm install wrtc Unable to find image 'node:9' locally 9: Pulling from library/node 3d77ce4481b1: Pull complete 534514c83d69:...
``` Kevs-MacBook-Pro:api kevzettler$ docker run node:9 node --version v9.11.1 Kevs-MacBook-Pro:api kevzettler$ docker run node:9 npm --version 5.6.0 Kevs-MacBook-Pro:api kevzettler$ docker run node:9 yarn --version 1.5.1 ```
@markandrus for the record. Even with this error, the module seems to behave as expected in my project.