-
-
Notifications
You must be signed in to change notification settings - Fork 824
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
deprecation warnings when used with node v6.0.0 #634
Comments
Hmm, I think this is coming from https://github.com/mapbox/node-sqlite3/blob/155e45ef57e49398fa396c31bcad4a6607b49e3a/src/macros.h#L58-L63. I presume this needs to be fixed in https://github.com/nodejs/nan but I'm not sure. |
Yeah, I think so too, just opened nodejs/nan#558 |
Watching fsevents/fsevents#128 too |
+1 |
+1 I was unable to install sqlite3 with node v6. |
Is there a way to suppress these warnings for now? I've tried |
Actually I think I figured out a way. I just rebuilt sqlite3 using nan 2.3.2 instead of the version it wants and the warnings go away. My app seems to be functioning fine. |
as per frankhale's suggestion, using nan 2.3.2 does indeed fix the warnings. |
Works for me too:
|
My pull request should fix this. However AppVeyor is saying it failed tests on Windows with node version |
Seems to be issues created: TryGhost/node-sqlite3#634 TryGhost/node-sqlite3#638
I wish to know what to put in the book I'm finishing. That is, I landed here due to testing the code for my book on Node.js 6.1, and getting errors like what's shown above. The book is all-but-finished and we're about to do the final round of editing (Node.js Web Development, 3rd edition) ... In the book I'm telling readers to install specific versions of various packages. If they were to follow the directions but be using 6.x they'll get those errors. It seems this specific fix is just a matter of updating the nan version dependency, and issuing a small release. I tried the workaround shown above and it worked fine. But I see other tickets on install problems on Windows and 6.x ... I'd rather update the book with a new version number - but no suitable version exists at the moment - but may have to put in a couple sentences suggesting to use a later version. |
@robogeek Fork this repo to your own GH account, include the necessary changes, and link / point to that in your book? If you leave a sentence or two explaining this people should be fine? Like this you'd be in control of the situation, though you'd have to make sure people won't keep trying to use your fork forever but instead are notified to go back to the upstream version soon. |
What about @zakdances's pull request? It's been in the queue for 14 days with no response. Yeah AppVeyor is complaining but maybe somebody familiar with that setup can help resolve the pull request issues and it can be merged? |
I can confirm that using @zakdances's fork solved this problem for Meteor. I know that's not enough to validate the changes, but at least they help! |
+1 (node) v8::ObjectTemplate::Set() with non-primitive values is deprecated ==== JS stack trace ========================================= Security context: 0x14c176bc9fa9 #0# ==== C stack trace =============================== 1: v8::Template::Set(v8::Localv8::Name, v8::Localv8::Data, v8::PropertyAttribute) |
@seanlarge I believe maintainer wish clean all ugly compile-time warnings (or have no time?) before publish new release, sure @kkaefer, @yhahn, @tmcw, @springmeyer? |
node-sqlite3@3.1.4 has been released, which is the first one to support node v6. |
Using sqlite with node 6.0.0 (just released) gives numerous warnings likely because of the changes made to address nodejs/node#6216.
The text was updated successfully, but these errors were encountered: