I tried just now, and it was working. Had some sort of b64=1 on it for me though.
app@buttoned-far-oriole:~ 22:16
$ DEBUG='*' node term.js
socket.io-client:url parse http://localhost:1084 +0ms
socket.io-client new io instance for http://localhost:1084 +0ms
socket.io-client:manager readyState closed +0ms
socket.io-client:manager opening http://localhost:1084 +0ms
engine.io-client:socket creating transport "polling" +0ms
engine.io-client:polling polling +0ms
engine.io-client:polling-xhr xhr poll +0ms
engine.io-client:polling-xhr xhr open GET: http://localhost:1084/socket.io/?EIO=3&transport=polling&t=NQHhM_c&b64=1 +1ms
engine.io-client:polling-xhr xhr data null +2ms
engine.io-client:socket setting transport polling +100ms
socket.io-client:manager connect attempt will timeout after 20000 +109ms
socket.io-client:manager readyState opening +5ms
engine.io-client:polling polling got data 96:0{"sid":"vfoZfOE_nVJJtQyWAAAF","upgrades":["websocket"],"pingInterval":25000,"pingTimeout":5000}2:40 +125ms
engine.io-client:socket socket receive: type "open", data "{"sid":"vfoZfOE_nVJJtQyWAAAF","upgrades":["websocket"],"pingInterval":25000,"pingTimeout":5000}" +28ms
engine.io-client:socket socket open +1ms
socket.io-client:manager open +69ms
socket.io-client:manager cleanup +0ms
socket.io-client:socket transport is open - connecting +0ms
engine.io-client:socket starting upgrade probes +54ms
engine.io-client:socket probing transport "websocket" +1ms
engine.io-client:socket creating transport "websocket" +0ms
engine.io-client:socket socket receive: type "message", data "0" +26ms
socket.io-parser decoded 0 as {"type":0,"nsp":"/"} +0ms
engine.io-client:polling polling +84ms
engine.io-client:polling-xhr xhr poll +206ms
engine.io-client:polling-xhr xhr open GET: http://localhost:1084/socket.io/?EIO=3&transport=polling&t=NQHhN2t&b64=1&sid=vfoZfOE_nVJJtQyWAAAF +0ms
engine.io-client:polling-xhr xhr data null +0ms
engine.io-client:socket probe transport "websocket" opened +78ms
engine.io-client:socket probe transport "websocket" pong +10ms
engine.io-client:socket pausing current transport "polling" +1ms
engine.io-client:polling we are currently polling - waiting to pause +87ms
engine.io-client:polling polling got data 11:42["login"] +4ms
engine.io-client:socket socket receive: type "message", data "2["login"]" +4ms
socket.io-parser decoded 2["login"] as {"type":2,"nsp":"/","data":["login"]} +93ms
socket.io-client:socket emitting event ["login"] +121ms
socket.io-client:manager writing packet {"type":2,"data":["resize",{"cols":211,"rows":53}],"options":{"compress":true},"nsp":"/"} +123ms
socket.io-parser encoding packet {"type":2,"data":["resize",{"cols":211,"rows":53}],"options":{"compress":true},"nsp":"/"} +2ms
socket.io-parser encoded {"type":2,"data":["resize",{"cols":211,"rows":53}],"options":{"compress":true},"nsp":"/"} as 2["resize",{"cols":211,"rows":53}] +1ms
engine.io-client:polling pre-pause polling complete +4ms
engine.io-client:polling paused +1ms
engine.io-client:socket changing transport and sending upgrade packet +75ms
engine.io-client:socket setting transport websocket +1ms
engine.io-client:socket clearing existing transport polling +5ms
engine.io-client:polling ignoring poll - transport state "paused" +78ms
engine.io-client:socket flushing 1 packets in socket +3ms
engine.io-client:socket socket receive: type "message", data "2["data","Welcome to the Glitch console\r\n\r\nIf you’re following someone else’s instructions make sure you trust them.\r\nIf in doubt post a question in our forum https://support.glitch.com\r\n\r\nFor now, the console and the editor don't automatically sync. You can\r\nmanually run the `refresh` command and it will force a refresh,\r\nupdating the editor with any console-created files.\r\n\r\nFor more information about this and other technical restrictions,\r\nplease see the Help Center: https://glitch.com/help\r\n"]" +91ms
socket.io-parser decoded 2["data","Welcome to the Glitch console\r\n\r\nIf you’re following someone else’s instructions make sure you trust them.\r\nIf in doubt post a question in our forum https://support.glitch.com\r\n\r\nFor now, the console and the editor don't automatically sync. You can\r\nmanually run the `refresh` command and it will force a refresh,\r\nupdating the editor with any console-created files.\r\n\r\nFor more information about this and other technical restrictions,\r\nplease see the Help Center: https://glitch.com/help\r\n"] as {"type":2,"nsp":"/","data":["data","Welcome to the Glitch console\r\n\r\nIf you’re following someone else’s instructions make sure you trust them.\r\nIf in doubt post a question in our forum https://support.glitch.com\r\n\r\nFor now, the console and the editor don't automatically sync. You can\r\nmanually run the `refresh` command and it will force a refresh,\r\nupdating the editor with any console-created files.\r\n\r\nFor more information about this and other technical restrictions,\r\nplease see the Help Center: https://glitch.com/help\r\n"]} +171ms
socket.io-client:socket emitting event ["data","Welcome to the Glitch console\r\n\r\nIf you’re following someone else’s instructions make sure you trust them.\r\nIf in doubt post a question in our forum https://support.glitch.com\r\n\r\nFor now, the console and the editor don't automatically sync. You can\r\nmanually run the `refresh` command and it will force a refresh,\r\nupdating the editor with any console-created files.\r\n\r\nFor more information about this and other technical restrictions,\r\nplease see the Help Center: https://glitch.com/help\r\n"] +174ms
term.js above is derived from snail-cli. My CLI for Glitch is called ‘snail’ 