Fix #3. #4
Merged
Fix #3. #4
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
|
@sebhildebrandt Could you please merge this? |
|
Thank you very much. |
|
Merged, will test it tomorrow and then release a new package version. Thank you! |
|
Merged and test, npm version 1.0.4 just released. |
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.
Add compatibility for Node 12 and fix deprecation warnings.
Pull Request
Fixes #3
Changes proposed:
Description (what is this PR about)
Brief explanation of the changes you have made and/or the new content you are contributing.
v8::Handle->v8::Local)ToString()andString::NewFromUtf8) to suppress deprecation warnings.Build succeeded on my MacBook with
node v12.6.0 / v10.6.0 / v8.16.0but did not do test runs.References: 1, 2