Skip to content
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

support node v12 #211

Merged
merged 2 commits into from
Jul 2, 2019
Merged

support node v12 #211

merged 2 commits into from
Jul 2, 2019

Conversation

nickdesaulniers
Copy link
Owner

  • upgrade nan to v2.14
  • use Nan::Utf8String rather than v8::String::Utf8Value

Fixes #206

- upgrade nan to v2.14
- use  Nan::Utf8String rather than v8::String::Utf8Value

Fixes #206
Looks like the Nan::Callback::Call() API deprecated bare calls that
don't pass a new Nan::AsyncResource().  Luckily, in this case we were
already subclassing Nan::AsyncWorker, which has a member named
`async_resource` so all we have to do is explicitly pass this along.

I wonder if Nan should just do this for me? *hmm*

Bug #209
@@ -5,7 +5,7 @@
"main": "lib/index.js",
"dependencies": {
"bindings": "1.2.1",
"nan": "2.8"
"nan": "2.14.0"

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a reason to depend on a specific nan version instead of ^2.14.0? Nan follows semver, releases are backwards compatible.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

precise versions guarantee what we're getting, but that sounds reasonable for nan, doing ^2.14.0 or 2.14

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we could

@@ -5,7 +5,7 @@
"main": "lib/index.js",
"dependencies": {
"bindings": "1.2.1",
"nan": "2.8"
"nan": "2.14.0"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

precise versions guarantee what we're getting, but that sounds reasonable for nan, doing ^2.14.0 or 2.14

@nickdesaulniers nickdesaulniers merged commit 668a167 into master Jul 2, 2019
@nickdesaulniers nickdesaulniers deleted the node_12 branch July 2, 2019 02:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Compile error in Node V12.*
3 participants