-
-
Notifications
You must be signed in to change notification settings - Fork 536
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
📝 more options that can be controlled from environment variables #190
Conversation
Thanks @basarat. Did you find out if those changes help you though, because that seems really odd. This is a TypeScript error and |
Thanks for the psychic debugging ❤️. Indeed it still happens. I'll track it down 🌹 |
If it helps, that error should be a TypeScript error. Definitely let me know what you find though 😄 |
I have the stack trace but haven't analysed it further:
Doesn't happen all the time. Will report back once I have a better analysed...just wanted to share in case something struck you immediately 🌹 |
Unfortunately the stack trace isn't terribly useful here since it's just a result of TypeScript compilation. TypeScript doesn't actually throw any errors, so this is TypeScript diagnostics thrown by I believe that error should only occur when an input file matches the output file by name, but I may be wrong. Seems odd that it would be an issue here though, since that directory is completely fake. I'll have to look more, feel free to make an issue so it doesn't get lost 😄 |
It seems like it should be from https://github.com/Microsoft/TypeScript/blob/0041d5ce7907f9ee974693ace54efd64afa1971a/src/compiler/program.ts#L2335. Seems odd, but is it possible this occurs on re-compilation somehow? Am I handling that incorrectly? So many user-land errors in TypeScript core I can't keep up! |
From :
ts-node/src/index.ts
Lines 96 to 97 in 44c389e
I actually needed to disable cache for alm.tools integrated test runner (alm-tools/alm#181) otherwise I get errors like the following sometimes:
😄 🌹