async connect Unexpected identifier about obs-websocket-js

[haganbmj]

What node version are you using?
I don't think async was made standard until node 7.6 or something.

I think you can run on 7.5 or something with node whatever.js --harmony?

[Kaliph]

Thankyou. Node 8.4 solved this issue. Thankyou for this hint!

[haganbmj]

Updated the project to hopefully ensure this doesn't happen in the future if people want to use older versions of node.
Try updating to obs-websocket-js v0.8.0 if you want to go back to an older node version and let me know if you run into any issues.

[Kaliph]

Ok. This is good news. Was already wondering how people on older node.js versions get this to work.. That said does that mean I can't run newer versions of obs-websocket-js with node.js 6.9 e.g. ? Am 23.08.17 um 23:09 schrieb Brendan Hagan

…

Updated the project to hopefully ensure this doesn't happen in the future if people want to use older versions of node. Try updating to obs-websocket-js `v0.8.0` if you want to go back to an older node version and let me know if you run into any issues. -- You are receiving this because you modified the open/close state. Reply to this email directly or view it on GitHub: #66 (comment)

[haganbmj]

Should work with any version of node > 4.
Tests are run with Node 4.8.4 and I've been working with Node 8.1.2.