Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
DeprecationWarning in node.js v7.0.0
See original GitHub issuewhen i use nodejs v7.0.0 and use this package and i use session store i get the error:
DeprecationWarning: Using Buffer without new will soon stop working. Use new Buffer(), or preferably Buffer.from(), Buffer.allocUnsafe() or Buffer.alloc() instead.
how fix ??
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Node v7.0.0 (Current)
Upgrade to Node.js v7 if you have the ability to upgrade versions quickly ... emitWarning to print deprecation warning (James M Snell) #8166 ......
Read more >Node.js deprecation warning and better developer experiences
Let's talk about v7 and the better developer experience it brings, discuss the Node.js deprecation warning and more.
Read more >DeprecationWarning · Issue #5184 · NodeBB ... - GitHub
Nodebb 1.3.0 fail with this error on nodejsv7: (node:5018) DeprecationWarning: Calling an asynchronous function without callback is deprecated.
Read more >Node.js 15 release: Updated handling of rejections, npm 7, N ...
In previous versions of Node.js, if there was an unhandled rejection, you would get a warning about the rejection and a deprecation warning....
Read more >Calling an asynchronous function without callback is ...
node --trace-deprecation app.js ... From Version: v7.0.0 ... [DEP0013] DeprecationWarning: Calling an asynchronous function without callback ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
haha, nevermind! The PR https://github.com/alexgorbatchev/node-crc/pull/44 was submitted to that module and merged not too long ago. Now we wait for a npm release 😃
Hi @c941010623 this module hasn’t been updated yet to really support Node.js 7.x (since it just arrived a few days ago), so thanks for making us aware of this new deprecation! You can add
--no-deprecationto your Node.js command line arguments to suppress the warning until we release an update.