Asher 31b67062b0 Remove <type> from onMessage ... Turns out that while Typescript can't infer the callback return type from it, Typescript can do the opposite and infer it from the callback return type.		2020-11-12 11:17:45 -06:00
..
routes	Refactor vscode init to use async	2020-11-10 18:21:20 -06:00
app.ts	Move websocket routes into a separate app	2020-11-05 15:08:09 -06:00
cli.ts	Fix bind address priority	2020-11-04 17:07:24 -06:00
coder-cloud.ts	cloud: Add mention of cloud repo	2020-10-09 12:57:48 -04:00
constants.ts	Add file for global constants	2020-10-26 17:56:12 -05:00
entry.ts	Move websocket routes into a separate app	2020-11-05 15:08:09 -06:00
heart.ts	Short-circuit heartbeat when alive	2020-10-27 17:48:37 -05:00
http.ts	Clarify some points around the cookie domain	2020-11-10 18:53:38 -06:00
plugin.ts	plugin: Make init and applications callbacks optional	2020-11-06 14:47:08 -05:00
proxy.ts	Move domain proxy to routes	2020-11-05 17:07:32 -06:00
settings.ts	Convert routes to Express	2020-10-26 17:56:13 -05:00
socket.ts	Read most recent socket path from file	2020-10-09 16:57:43 -05:00
update.ts	Fix destroying response in update again	2020-11-05 15:08:10 -06:00
util.ts	Move isFile into util	2020-11-03 15:27:20 -06:00
vscode.ts	Remove <type> from onMessage	2020-11-12 11:17:45 -06:00
wrapper.ts	Provide a way to tell when event handlers are finished	2020-11-05 15:08:07 -06:00
wsRouter.ts	Close sockets correctly	2020-11-10 17:55:04 -06:00