Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Question: reliability issues

See original GitHub issue

Hi,

We’ve switched to using this for our slightly larger codebase, and encountered various, indeterministic errors when importing from local modules.

I know this is a very vague ticket, just want to record this issue. We’ve reverted back to the original setup - using tsc --watch. (we were using es2015 modules, and the recommended configuration)

Has anyone else encountered weird issues? We had local modules imported as undefined, which we couldn’t resolve.

I think this may be connected to how transpileModule vs tsc works, but I could be easily wrong.

Issue Analytics

State:
Created 6 years ago
Comments:8 (4 by maintainers)

Top GitHub Comments

1reaction

ds300commented, Oct 1, 2017

We resolved this today. There was in fact a cyclical dependency issue. It might be that TypeScript is able to emit code that works around certain cyclical dependencies when operating on a program level with tsc, but not when operating at a module level with transpileModule, as is done in react-native-typescript-transformer. It’s worth mentioning that the problem turned out to be deterministic.

I’ll add a note to the README about possible introduction of cyclical dependencies when transitioning an existing TS codebase from tsc to react-native-typescript-transformer, and then close this issue.

Thanks @itchingpixels for your help 🙏

0reactions

itchingpixelscommented, Oct 2, 2017

thank you for your help identifying this issue!😃 On Sun, 1 Oct 2017 at 23:36, David Sheldrick notifications@github.com wrote:

We resolved this today. There was in fact a cyclical dependency issue. It might be that TypeScript is able to emit code that works around certain cyclical dependencies when operating on a program level with tsc, but not when operating at a module level with transpileModule, as is done in react-native-typescript-transformer. It’s worth mentioning that the problem turned out to be deterministic.

I’ll add a note to the README about possible introduction of cyclical dependencies when transitioning an existing TS codebase from tsc to react-native-typescript-transformer, and then close this issue.

Thanks @itchingpixels https://github.com/itchingpixels for your help 🙏

— You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub https://github.com/ds300/react-native-typescript-transformer/issues/30#issuecomment-333412029, or mute the thread https://github.com/notifications/unsubscribe-auth/AFKlYBSZGgXsMDKKG5cPdnmPwDvxpr3Zks5soBPqgaJpZM4PkKMK .