Frank Wallis

I found that this was happening when I had linked modules with ```npm link```. Setting webpack ```resolve.symlinks: false``` seems to have resolved it for me. https://webpack.js.org/configuration/resolve/#resolve-symlinks

I think this could be due to the ```rootDirs``` option, what exactly is it for? As this setting is related to module resolution, and runtime module resolution is handled entirely...

Also see https://github.com/Microsoft/TypeScript/issues/12246 as it sounds very similar.

Thank you for taking the time to do this, it is really appreciated and it would be great if we can get to the bottom of some of these interoperability...

I am happy to change this, but how would you expect it to work in the situation where you have file-level typescriptOptions as well as global typescriptOptions defined? Currently the...

Yes, I am open to a pull request but I would like to know what the impact will be on existing users. I think that all tsconfig handling would be...

Possibly this could be done by exposing the TypeScript CompilerHost globally so that it could be shared with a separate AoT plugin? It's not really something I would want to...

plugin-typescript now exposes a global variable `tsfactory` which is a `Promise` and would enable other plugins to access the CompilerHost used by plugin-typescript (along with the Resolver, TypeChecker and Transpiler)....

Looking at the first issue it seems that the file is not getting passed through the transpiler, I'm not exactly sure why, but it's likely to be a configuration issue.

There is some info in the release notes (https://github.com/Microsoft/tslib/releases) ``` NOTE: This is a breaking change from TypeScript 2.3.2 and earlier when using tslib with async generators: If you are...