Function import path not correct in tamagui example about grats HOT 4 CLOSED

I think I see the issue here. There is a tsconfig.json in the repo root and also one in apps/vertql-example. Unless you specify a specific tsconfig via a config option or cli option, Grats will fallback to finding one relative to the current working directory. I suspect the schema was generated with grats running in the root dir, and then when it runs from within the project directory it ends up using a different tsconfig.

The issue is that we rely on the tsconfig to tell us where the .js version of the file is going to be placed. So we are looking for js file where the root config would have put it rather than where the example app's tsconfig is actually putting it.

Need to think more about how we can avoid this issue or at least provide a more helpful error message.

from grats.

Looking more closely, this wasn't the actual issue. I now believe the actual issue is that the setup in tamagui is to use esbuild-register to dynamically convert typescript to javascript at runtime. This breaks our dynamic imports because they expect the .js file to exist on disk.

Possible mitigation/solution is to include both the js module and ts module in the directive and use a try/catch to try each one, perhaps with some caching?

from grats.

Exploring a fix here: #56

from grats.

Reopening as the issue still reproduces even after #56

from grats.