These are chat archives for TypeStrong/atom-typescript

16th
Nov 2015
David Driscoll
@david-driscoll
Nov 16 2015 03:32
babel hates me, I'm convinced
Basarat Ali Syed
@basarat
Nov 16 2015 04:46
@david-driscoll its because you use typescript :P
it knows
David Driscoll
@david-driscoll
Nov 16 2015 04:57
lol
I figured it out, it was the cwd :fearful:
Basarat Ali Syed
@basarat
Nov 16 2015 04:58
good to know for future things that don't work if debugSync is false < Haven't run into this before :)
David Driscoll
@david-driscoll
Nov 16 2015 05:01
was really strange... I guess cwd must be managed somewhere else, but I've only ever glanced at the atom-typescript code
trying to convert omnisharp-client/atom to RxJS 5, see if there is anything blocking... so far so good, just growing pains.
@david-driscoll the whole of our worker handling is a bit untidy. Cleaned that up in a simpler contract master worker workflow : https://github.com/TypeScriptBuilder/tsb/blob/master/docs/contributing/ASYNC.md
I'll port it back at some point ... or leave it as an OSS up for grabs feature when / if I factor out that code to a seperate NPM module
David Driscoll
@david-driscoll
Nov 16 2015 05:05
yeah, I explored trying to do something like that for a time with omnisharp-client.. I need to get back to it when I have real time to dedicate to it.
would love to have a central process that manages all the omnisharp processes, and can be shared by many atom windows, offload all the event loop blocking to that process. :smile: