⚠️ Unnecessary addition ____exports

[idrevnii]

Describe the bug

If you call an exported function in its own file, the build will add ____exports to its call, which will result in nil in the runtime.

To Reproduce

Steps to reproduce the behavior:

1. Create two files first.ts and second.ts
2. In first.ts write two functions export function func1 () { ... } and export function func2 () { func1() }
3. In second.ts write function function func3() { func1(); func2() }
4. Built this and in file first.lua in func2 insead of func1() call will be ____exports.func1() which will lead to nil in runtime

Expected behavior

Correct functional call

Screenshots (If my explanation is unclear :D)

[Toliak]

Looks like TSTL determines, that the function is being exported and adds its magic :)
I am not sure about fixing timing, however I have a workaround for you)

You can insert this into the first loaded script (or into all scripts). This will reference ____exports to _G, Lua's global table

let ____exports = null;
// eslint-disable-next-line @typescript-eslint/no-unused-vars
____exports = globalThis;

---

Possible fix (for me): create a new visitor, that will check all function calls and change ____exports to _G