Basarat Ali Syed

No not expected. I don't know why it's happening. If you can share your code I can have a look. Sorry I missed this message somehow :rose:

I have a fork here : https://github.com/basarat/takeme where the demo works. The demo for yester might be up once we are done with migration over to @mattoni (ref https://github.com/basarat/yester/issues/15) :rose:

> This would allow me to handle repetitive data loading tasks without doing it multiple times, nest route views, etc. You can simply move out the functions and call them...

Suggestion: Only support _inline source maps_. These contain the _contents_ of the original file _within_ the source map. You can display these files as a pseudo file within atom

Nevertheless .... lots of work. Thanks for the package even as it stands right now :rose:

> TypeScript 2.0 didn't change too much, really. @vkurchatkin going through your examples: 1. https://github.com/vkurchatkin/typescript-vs-flow/blob/master/ts/1.ts also fixed with `strictNullChecks` 1. https://github.com/vkurchatkin/typescript-vs-flow/blob/master/ts/2.ts also fixed 1. https://github.com/vkurchatkin/typescript-vs-flow/blob/master/ts/3.ts also errors in ts 1....

Another example where managing *just with js would help*, you wouldn't need to give this warning as the CSS can be generated on the fly 

> always a pleasure to hear your input and see what you're working on! Mutual respect for all your OSS efforts as well :rose: :heart: and Thanks! > Doesn't this...

I agree that it is too much. > However I hate having to restrict access to just folks using JavaScript or TypeScript, and the easiest way to get other runtimes...

Plausable. I've moved on to https://github.com/basarat/byots : using it for http://alm.tools/ and will migrate atom-typescript to that as well when I get some time :rose: