Blake Embrey

I believe this is the same issue as https://github.com/TypeStrong/ts-node/issues/1421, which is due to how TypeScript is unfortunately repeated invoked on files. It doesn't release this is outside the scope of...

Discussed in https://github.com/TypeStrong/ts-node/issues/811. It'd be nice but isn't possible at this time because the API doesn't exist.

@ohjames that looks unrelated to this issue, please keep it separate. This issue is specifically around using the incremental compilation API available in TypeScript. The solution you’ve written is actually...

@tangentlin It's supported on `master` but is not available for release. The TypeScript build cache hasn't had any measurable effect that I can see so I'm probably using the API...

Anyone reading this or other issues is welcome to pitch in and open a PR, right now I just don't have the personal bandwidth to figure it all out.

You’re correct, it is available for people! Please test it. But unfortunately it doesn’t cover the references use-case yet, which means it’s not on by default. It’s possible to workaround...

@chpeters I'd guess that would be because `graphql` is actually CommonJS and not an ES module. You can read more about it here: https://nodejs.org/api/esm.html#esm_interoperability_with_commonjs. Unfortunately it'll probably be messy for...

There's no great way to do this except for throwing an error and making it impossible for your code to execute. If I silently allow one and not the other,...

@ZSkycat Do you have a suggestion for how this could be detected? My only thought is storing a global that can be accessed somehow by all modules, but I have...

@ZSkycat It looks like two issues: 1. You might misunderstand `cross-env` - you need to remove the `&&` since it would be executing `ts-node` without the environment variable (says run...