We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I used why-is-not-running in node 12 with much satisfaction but now I've upgraded to the node 16 LTS it is not working anymore for my use-case.
The native Node crypto module now gives a lot of RANDOMBYTESREQUEST false positives.
I think this is related to an issue on Jest: jestjs/jest#11275. Their fix: https://github.com/facebook/jest/pull/11278/files
The text was updated successfully, but these errors were encountered:
6708b2e
Nice, good catch. I tried to push a fix, can you test it?
Sorry, something went wrong.
Great, works perfect!
Update why-is-node-running to latest
9f87b22
Avoids reporting thousands of RANDOMBYTESREQUEST handles. See mafintosh/why-is-node-running#57
b31331f
No branches or pull requests
I used why-is-not-running in node 12 with much satisfaction but now I've upgraded to the node 16 LTS it is not working anymore for my use-case.
The native Node crypto module now gives a lot of RANDOMBYTESREQUEST false positives.
I think this is related to an issue on Jest: jestjs/jest#11275. Their fix: https://github.com/facebook/jest/pull/11278/files
The text was updated successfully, but these errors were encountered: