When there is a Javascript error, Socket.IO disconnect and prevent debugging

so i don't know if it's a new thing in socket.io 1.1.0 but whenever i have a javascript error, anywhere in my code (even when it doesn't involve socket.io at all), socket.io is simply disconnecting (it calls the disconnect event and also the error event with an TransportError error) and then... nothing shows up in the firefox console nor chrome console, no debug info, nothing, and it doesn't help me to find the error...

is there a way to prevent socket.io to do that or is it a thing to do with websockets or something ?