Closed CraigChilds94 closed 8 years ago
Note: updating to v0.12.2
didn't appear to do anything.
It appears as though getting a response regarding this matter is pretty slow?
Sorry. I missed this issue. Can you share the cli commands you are running?
I'm running the ones which were specified in your README
I'm running into this too. After a fresh checkout from master and a clean npm install
I run:
./bin.js listen -p 8080
and then in another terminal I run
./bin.js broadcast test channel '{"test":"hello"}' -p 8080 -h localhost
and nothing echoes in the listening terminal (looking at ./bin.js it seems like something should)
I'm running node v4.1.0
Should be fixed in the latest version by @diffalot
Hey there, I wanted to test this out because it looks really cool and easy to use. I thought I'd give the CLI examples a go but it doesn't appear to be doing anything.
I can listen on a port without errors being thrown but when I broadcast or subscribe it doesn't appear to be picked up. Nothing is being logged.
Maybe my version of Node doesn't like console.log? It's
v0.10.29
It'd be great if you could help me out or let me know where I might be going wrong?