test with socket.io 0.8, then possibly bump dependencies

A few months ago when I initially installed and configured this module it worked great with FF and Chrome. Recently, however, I noticed I was getting a socket err with Chrome but FF still worked fine. This evening I updated socket.io to 0.8.4 and all seems well again. My npm ls looks like:

s
├─┬ connect@1.7.1 
│ ├── mime@1.2.4 
│ └── qs@0.3.1 
├─┬ express@2.4.6 
│ ├── connect@1.7.1 
│ ├── mime@1.2.4 
│ └── qs@0.3.1 
└─┬ socket.io@0.8.4  invalid
  ├── policyfile@0.0.4 
  ├── redis@0.6.6 
  └─┬ socket.io-client@0.8.4 
    ├── uglify-js@1.0.6 
    ├── websocket-client@1.0.0 
    └── xmlhttprequest@1.2.2 

soket.io is being marked as an invalid dependency, but I assume that is because express and connnect have not been updated to reference the new socket.io version. Regardless I have yet to encounter issue.

I must note that I've only tested this with the nodejs_notify as it is all I am presently messing with. So this is hardly a thorough test. Just thought I would chime in here.

EDIT: I realize after the fact that my assumption is somewhat silly, the dependency is likely the very one you are referencing in the issue.

I ran under localhost nodejs run very well but I put it on the server then this error you help me.
publicMessageToContentChannel: Thr chanel "watchdog_dblog" doesn't exitst

@supermouse

Watchdog didn't work until #1192450: fix broadcast of watchdog messages, so it was a common problem. Try with dev version that has this patch.

I've tested my mobile app that uses websockets to integrate with Drupal:

├─┬ connect@2.2.1 
│ ├── crc@0.1.0 
│ ├── debug@0.6.0 
│ ├── formidable@1.0.9 
│ ├── mime@1.2.4 
│ └── qs@0.4.2 
├─┬ express@2.5.9 
│ ├─┬ connect@1.8.7 
│ │ └── formidable@1.0.9 
│ ├── mime@1.2.4 
│ ├── mkdirp@0.3.0 
│ └── qs@0.4.2 
├── request@2.9.202 
└─┬ socket.io@0.9.6 
  ├── policyfile@0.0.4 
  ├── redis@0.6.7 
  └─┬ socket.io-client@0.9.6 
    ├─┬ active-x-obfuscator@0.0.1 
    │ └── zeparser@0.0.5 
    ├── uglify-js@1.2.5 
    ├─┬ ws@0.4.14 
    │ ├── commander@0.5.2 
    │ └── options@0.0.3 
    └── xmlhttprequest@1.2.2 

And evererything seems to work fine.