-
Notifications
You must be signed in to change notification settings - Fork 44
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
Arkit crash during running on medium size project #28
Comments
@davojta Thanks for the bug report! |
I've got a very similar issue with 1.3.14 https://gist.github.com/karevn/c0cda153fb233c74b38cd847fb4399e8 |
@karevn actually, it's a bit different and I suspect it's related to Node version. Could you please update arkit to 1.3.16 and try again? |
I've upgraded to 1.3.17, exactly the same error. Node.js version 8.11.2, and upgrading it is not an option in the meantime. |
Still have the same issue on 1.5.3
|
@karevn have you been able to resolve the issue? I have the same problem with both node10 and node13, btw I run on macOS |
same issue |
same here |
Hi all. I was having this issue too and I did some investigation. The thing is there are some libraries that use some reserved JS properties as the filename. In my case, the filenames causing the error were I just created a PR (#710) to fix this issue. cc: @dyatko |
In my case today, the problematic files were from lodash. I could work around it by excluding those directories too, but I only found the culprit after debugging. I imagine many people are using Arkit to get a better understanding of a legacy code base, so it might make things much much easier to have more robust handling of the names. |
Bug description
To Reproduce
Ubuntu 16/04
1.3.13
I run on my project, so cant share it whole source base
The text was updated successfully, but these errors were encountered: