Typescript Inference Issues in Monorepos with Cross-Package Boundaries
I have a reository setup as a monorepo, and I'm facing some typescript inference issues. For example, in my two screenshots you can see how one of my methods return an effect that has a dependency, but at the call site the program using it is not getting that attached. Instead, I see any in the requirements type. Can anyone point me to common pitfalls in monorepos? This particular example is crossing "package boundaries", meaning that the method is defined in one package and it is being consumed in "one app"
Similar Threads
Was this page helpful?
