-
Notifications
You must be signed in to change notification settings - Fork 12.8k
Internal typescript error with no useful information #8961
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
Comments
can you share the repro scenario for this issue? |
Unfortunately, no. I can't narrow down what's causing this in a repo of several hundred files. I'm hoping someone has tips on what might be causing this or troubleshooting steps so I don't have to just poke blindly... every similar error I saw while researching this error referenced the user's code above the stack trace... it seems like this is being thrown by TS from TS. |
can you try using node-inspector to debug the tsc.js process: npm install -g node-inspector
node-inspector
node --debug-brk <path to your tsc.js> somewhere on the stack, there should be a call to |
also a longer stack trace would be helpful. for that try:
|
Thanks @mhegazy! I was never able to get an isolated repro for this but I did narrow it down to 3 problem files and it seemed to be related to binding functions in the constructor? Removed those and now it all compiles. ¯_(ツ)_/¯ |
was this a .js or a .ts file? we would love to figure out the issue and fix so you do not have to change your code. |
It was a |
is there any chance you can share a sample? we would be happy to sign any NDA to get access to the code. |
Let me check with my manager. I'll also try to revisit this by the end of the week and try to figure out what actually happened. I'm in a bit of a rush right now because I'm blocking people. |
I'm encountering this error at the moment as well (found this issue via Google). It sounds a lot like this issue which was fixed in 2.0.2 (although 2.0.0 hasn't been released yet which I've got to admit I'm totally confused about :-) ). |
Yup - installed 2.0.2 via npm and it made this error "go away" for me. Assuming that it is the same error (it sure sounds like it) I think this is resolved. |
This happened to me as well, there is no details to error just In my case it was because I left git conflict unresolved with |
I'm trying to compile an existing codebase and getting an error message with no useful context at all and which doesn't reference any of my code. Any pointers here?
The text was updated successfully, but these errors were encountered: