TypeScript support

[guybedford]

Just to try and bring everything into one place, I have the following issues pending:

• TypeScript sourcemaps support #177 Source Maps support
• TypeScript helper separation #178 Helper sharing / separation
• TypeScript bundling should generate compile errors #206 Compile errors when bundling in TypeScript
• Enable TypeScript tests #200 Enable TypeScript tests

Is there anything else here I'm missing? Please post here if anyone is working on any of these, otherwise they probably should be prioritised in terms of user experience benefits. Will aim to find some time myself too if necessary.

//cc @robwormald @vladima

[guybedford]

The alternative here would be to focus work on the TypeScript plugin rather and make that the core experience, as it is being actively driven by @frankwallis.

[vladima]

#177 and #178 are scheduled for TypeScript 1.6 which is the next TypeScript release.
Re: #200, I'm working on it, related question: clean npm install fails with the following error:

npm ERR! peerinvalid The package phantomjs does not satisfy its siblings' peerDependencies requirements!
npm ERR! peerinvalid Peer mocha-phantomjs@3.6.0 wants phantomjs@1.9.1 - 1.9.7-15

[guybedford]

@vladima thanks so much for the update! I assume that issue is running npm3? Perhaps force downgrade the phantomjs dependency in the package.json to 1.9.7 and see if that helps?

[vladima]

@guybedford I've tried to enable tests for TypeScript and it seems that currently the majority of failures happens because TypeScript does not have built-in support for remapping dependencies (similar to Traceur or Babel). Is it something that should be resolved on TypeScript side or you have some way to workaround this issue?

[vladima]

Ok, I guess this intended to be the answer to my previous questions. Unfortunately I don't think that custom resolvers will solve the issue. Currently they are only used to help TypeScript compiler resolve names of imported modules (i.e. if during development imported modules are fetched on demand from some file share) and they does not affect code generation - module name in generated javascript will be exactly the same as it is was written in original .ts file. What we probably can do is provide a way to pass depMap to the compiler so during emit if depMap was provided it will be used to rename items in dependency list

[guybedford]

After the current merges, all that is left now is helper separation and compilation error reporting. Closing as this means we have the baseline covered now.