-
-
Notifications
You must be signed in to change notification settings - Fork 129
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
Added noop callback (Node 7.0 deprecation warning) #91
Conversation
@andris9 can you please merge this? although, I'd like this to throw an error if there is an error. |
@andris9 Please release this change. Its flooding logs at the moment. |
@Dexus can you please do the release? It would be nice to add either more people to NPM or use something like https://github.com/semantic-release/semantic-release to automate the release process. |
Yeah i will do, but currently i'm on a business trip so it will maybe two weeks. Have here no key for my system. Regards, Von meinem iPhone gesendet
|
Can you add me as a collaborator to NPM? This can be done via the web UI. My username is "gajus". |
From here i'm also unable to login to NPM. I have only my work laptop and not access to any private keys and passwords. Regards, Josef Von meinem iPhone gesendet
|
This is a follow up to https://github.com/andris9/pem/pull/91, ensuring that errors from fs.unlink() calls get bubbled up correctly. This also ensures all fs.unlink() calls have a callback, which is important to avoid deprecation warnings on Node 7.
This is a follow up to https://github.com/andris9/pem/pull/91, ensuring that errors from fs.unlink() calls get bubbled up correctly. This also ensures all fs.unlink() calls have a callback, which is important to avoid deprecation warnings on Node 7.
No description provided.