Perry van Wesel

Investigation result: This is default TypeScript behavior. There are [some issues](https://github.com/microsoft/TypeScript/issues/8305) on their repo discussing this. It does not try to resolve declaration files referred to by your files. In...

Workaround for now: add require path to noResolvePaths in tsconfig. For missed requires there is unfortunately no real workaround other than copying the lua files yourself manually/with a build pipeline/with...

Results of some investigation, there are seemingly multiple issues: 1) Cloth sim indeed seems part of the problem. The model I saw is broken because the cloth bones have no...

We have the `@noResolution` compiler annotation for exactly this scenario: [see the docs here](https://typescripttolua.github.io/docs/advanced/compiler-annotations#noresolution)

Aha, I see what you mean. I'm thinking we could probably add some list of non-resolve libraries to the configuration, and check those when a require inside a .lua file...

Even if the lua file has no TS source, we still need to make sure that the files it requires exist, there is no way to tell from an included...

With `1.1.0` released 2 days ago we also added the `noResolve` tsconfig option, which lets you specify paths you dont want to be resolved in your tsconfig. Would that fit...

Not really interested in doing this, `--watch` mode already kind of solves this with incremental compilation, which does the caching as you describe as long as the watcher is running.

Is this really about translating `console.log(x)` to `print(tostring(x))` instead of just `print(x)`? Or would we want to do some more logic there where we'd check if `x.__tostring` or `x.tostring` is...

Thanks for the issue, using [[ ]] strings is an interesting suggestion leading to potentially more readable generated code. TypeScript strings with `` ` `` are more than just multi-line...