Nicholas Jamieson

I guess it doesn't work because tsify passes its own compiler host to TypeScript - to abstract the file system - as the compiled files need to be made available...

Cool, I'll write up some pointers tonight - in about 6 hours or so. The main thing will be to switch [debugging](https://github.com/TypeStrong/tsify/blob/master/CONTRIBUTING.md#debugging) on and checkout the logs - to see...

@ericmorand I'd forgotten that I'd written an outline of the codebase. You should start with that. It's [here](https://github.com/TypeStrong/tsify/blob/master/CONTRIBUTING.md#internals-and-processing-flow). Once you've familiarised yourself with that, this is what I'd do: *...

Yep. Probably worth having a look at - or keeping an eye on - https://github.com/TypeStrong/ts-loader/pull/935 too.

> I think this types definition is the correct one: ... Yeah, you are right. If you want to open a PR for the change, that would be appreciated. >...

Incremental TypeScript compilation is not supported.

None of the project related features added in Typescript 3.0 are supported. I've not used tsify for years, now, and don't have the time to add features - or even...

@CheyenneForbes > ... are you open to passing on the project to a new maintainer? It wouldn't be up to me and I doubt it would just be "passed on"...

@SteffenAnders Browserify's `paths` option is not something I've spent time investigating. In any case, I don't believe that it's up to tsify to support it. TypeScript and Browserify both perform...

I'm not going to merge this. You have an issue because you are using a specific, pre-release version of TypeScript and I guess that npm - unlike Yarn - doesn't...