TcpSocket.js#L11 overwrites the process global. This causes existing process.env values to be lost. I think this library should leave it to the end-user to shim the global process object (example). Regardless, I don't think it should clobber existing process.env values as it causes the rest of my program, which depend on the process.env values, to fail.