@basarat, I think this makes it much easier to work on the code. I have a few things I need to add before I can use this in the office. After this I intend to attempt to rectify the 600+ ms startup time, and depricated api usage.

Glad I didn't do a push. I'll merge and then commit my stuff ❤️

Including map files to make debugging simpler.

did it really help? I didn't see atom picking it up when I tried : #123

Nope. Sourcemaps don't work :

It's because our JS gets wrapped by atom in (function (exports, require, module, __filename, __dirname) { and });

So sourcemaps are no longer valid :

I'd be more interested in adding TypeScript support directly into atom once I get a chance. Looking at the recent 6to5 support its not that hard to do.

@park9140 also, we are building with atomts instead of grunt : 6134350

grunt is now there just for backup (when things go bang during development). Also note const enum handling is broken in the 1.4 language service : 6134350#diff-4e626b81616e50c89d68cba32c8d4c51L34 so if the last build isn't from atomts then the output would mismatch and there will be conflicts 👍

@park9140 also, we are building with atomts instead of grunt : 6134350

Nobody will know if the documentation is not kept up to date :) https://github.com/TypeStrong/atom-typescript/blob/master/CONTRIBUTING.md#building

@csnover on it

@park9140 if sourcemaps indeed don't work for you as well delete them from the repo, grunt file,tsconfig. Or give me the go ahead ❤️

@basarat, will do, I popped my debugger up and thought I was seeing them, but I'll take another look, maybe I had some weird setting, I played with adding direct typescript support before and may have enabled something that made them work.