Fix deprecation warnings in Node 10.12 & 11 builds #287
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jhecking
force-pushed
the
node11-deprecation-warnings
branch
from
45371d3 to
fbc8ed0
Compare
Codecov Report
@@ Coverage Diff @@
## master #287 +/- ##
=======================================
Coverage 97.15% 97.15%
=======================================
Files 44 44
Lines 1512 1512
=======================================
Hits 1469 1469
Misses 43 43Continue to review full report at Codecov.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
ToString,ToObject, ... functions--debugto see all warnings)nanpackage with fix for Fix deprecation warnings on node 10.12 nodejs/nan#811 (once available)