Closed MrRefactoring closed 3 years ago
Hey @MrRefactoring,
Thanks for reporting it. can you please provide package.json
and yarn.lock
please. that would be helpful to debug the issue.
package.json
+ yarn.lock
:
data.zip
Thanks @MrRefactoring
Hmmm. seems like you have so many vulnerabilities that even stream buffer limit in Node is reached. :)
I don't have any way to fix this in my package as of I don't have control on that limit. But I have a solution that might help you to use my package without errors.
Try doing yarn audit --json > audit.json
and then with separate command cat audit.json | yarn-audit-html
. This will separate Buffer usages in Node between two commands so they will not reach the limit.
Here, you can find attached audit report for your repo.
Thanks again fro reporting this issue. ;) Feel free to close this issue if it resolves your problem.
yarn audit --json
returns 3.1 GB data. And when I executed yarn-audit-html I got an error: