-
-
Notifications
You must be signed in to change notification settings - Fork 221
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
Error: toString failed #100
Comments
Strange, how about |
Same error with |
It sems related to node.js: nodejs/node#2767 Are there large files in your project? |
@harshjv do you have any update on this issue? I am going to close this issue if you have no reply in 1 day. |
I'm having the same issue. |
@veob do you have a large file in your project? |
@lijunle |
Depcheck not only read for |
@lijunle |
OK, let me assume that 1M in this case. Besides, how many files under your project folder? |
~1400 .js files (excluding node_modules/ obviously) |
Hm. I've just ran |
@veob thanks for your information. I will test offline tonight and revisit here later. |
@veob Sorry that I tried different ways, however cannot repro this issue. Are you still getting this exception? Could you provide more information?
|
node version: Just so you know, It's not critical for me to check dependencies for this particular project and if you wouldn't be able to reproduce and fix this issue, for me personaly it's okay. Don't about other people though. |
@lijunle I'm having the same issue. I do use ES6/harmony features and generators (koa app). I'm not sure if this impacts anything. node version: |
I am considering it is caused by binary files (either custom binary file or node.js addons). I am not having time to verify it. Could you please help to verify it? Great thanks. |
@lijunle I'm not sure what you mean. I checked and the biggest JSON file that I had was 1.3MB. I removed that file and still no luck. |
@jmealo do you have binary files in your project folder? If yes, could you please remove them and re-run depcheck? |
Hey, everybody here. After release v0.6.3 to npm-check, I don't get similar issues. Does anybody still getting this issue (with newest node.js)? |
@lijunle I have this issue with v0.6.3 |
Pluggable design change.
I'm closing this issue due to no activity in 2 years. Please feel free to open a new issue if this issue is seen again! |
Error: toString failed
when used withnode v4.3.1
$ depcheck
The text was updated successfully, but these errors were encountered: