-
-
Notifications
You must be signed in to change notification settings - Fork 25
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
Consider changing dependencies #13
Comments
We're also having issues due to this in our code. |
+1 here would be great to swap dependencies |
Any updates ? |
Sorry everyone I have been away for a few weeks Ill get this sorted out now. |
You rock, thank you.
On 3 Oct 2017, at 11:41, Maurice Butler <[email protected]<mailto:[email protected]>> wrote:
Sorry everyone I have been away for a few weeks Ill get this sorted out now.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#13 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AAYF3FGviTbPEXTsC_WJgi8zDJS4WH0gks5sog9EgaJpZM4O28A3>.
|
FYI version 1.3.0 is now published which has been updated to use This version should now install with no security warnings. Due to some missing functionality in the As soon as the loggly/node-loggly-bulk#21 PR is merged I will release another version to bring back the bulk sending. I will close this issue now and have raised #18 to track the change to re-enable bulk processing |
Please consider updating the dependencies. Right now we have
node-uuid
generating warnings:[SECURITY] node-uuid: crypto not usable, falling back to insecure Math.random()
Tracking back ... loggly package seems to be unmaintained (issue open five months back without answers). Loggly team created a fork repo to keep up security updates and created a new package.
The text was updated successfully, but these errors were encountered: