Security News
Research
Data Theft Repackaged: A Case Study in Malicious Wrapper Packages on npm
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Tool to turn functions with Node-style callback APIs into functions that return Promises
The denodeify npm package is used to convert Node.js-style callback functions into promises. This is particularly useful for working with asynchronous code in a more readable and manageable way using modern JavaScript features like async/await.
Convert Node.js callback functions to promises
This feature allows you to convert a Node.js-style callback function, such as fs.readFile, into a function that returns a promise. This makes it easier to work with asynchronous code using promise chaining or async/await.
const denodeify = require('denodeify');
const fs = require('fs');
const readFile = denodeify(fs.readFile);
readFile('example.txt', 'utf8')
.then(content => {
console.log(content);
})
.catch(err => {
console.error(err);
});
Using with async/await
This feature demonstrates how to use the denodeify package with async/await syntax. By converting the callback-based function to a promise-based one, you can use the more modern and readable async/await syntax to handle asynchronous operations.
const denodeify = require('denodeify');
const fs = require('fs');
const readFile = denodeify(fs.readFile);
async function readFileAsync() {
try {
const content = await readFile('example.txt', 'utf8');
console.log(content);
} catch (err) {
console.error(err);
}
}
readFileAsync();
The util.promisify function is a built-in Node.js utility that converts callback-based functions to promise-based ones. It is similar to denodeify but is part of the Node.js standard library, making it a more integrated and often preferred solution.
Bluebird is a fully-featured promise library that includes a promisify function similar to denodeify. Bluebird offers additional features like cancellation, progress tracking, and more, making it a more comprehensive solution for working with promises.
Pify is a lightweight library that converts callback-based functions to promise-based ones. It is similar to denodeify but is designed to be more flexible and easier to use with a variety of different callback patterns.
Tool to turn functions with Node-style callback APIs into functions that return Promises.
Inspired by and adapted from Q's Q.denodeify
/Q.nfcall
function.
Warning: This micro-library doesn't force you to use any particular Promise implementation by using whatever Promise
has been defined as globally. This is so that you may use any ES6 standard Promise compliant library - or, of course, native ES6 Promises.
If you're running the code on a browser or node version that doesn't include native promises you will need to include a polyfill. The following polyfills are tested as part of this module's test suite:-
require('es6-promise').polyfill();
require('native-promise-only');
require('es6-shim');
global.Promise = global.Promise || require('lie');
Note: as of v1.2.0 you can use denodeify in the front end. Pull it in via CommonJS, AMD or simply add to your webpage and it'll be available on window.denodeify
.
npm install denodeify --save
Or:-
bower install denodeify --save
Simple example with readFile
:-
require('es6-promise').polyfill();
var denodeify = require('denodeify');
var readFile = denodeify(require('fs').readFile);
readFile('my-file.txt', { encoding: 'UTF-8' })
.then(function(text) {
console.log("My file's contents is: " + text);
});
(Note: you will need to also install es6-promise with npm install es6-promise
for this code sample to work within node versions that don't have Promise
natively available)
More complex example with exec
:-
You can also pass in a function as a second argument of denodeify
that allows you to manipulate the data returned by the wrapped function before it gets passed to the Promise's reject
or resolve
functions, for example:-
require('es6-promise').polyfill();
var denodeify = require('denodeify');
var exec = denodeify(require('child_process').exec, function(err, stdout, stderr) {
// Throw away stderr data
return [err, stdout];
});
exec('hostname')
.then(function(host) {
console.log("My hostname is: " + host.replace('\n', ''));
});
Or,
require('es6-promise').polyfill();
var denodeify = require('denodeify');
var exec = denodeify(require('child_process').exec, function(err, stdout, stderr) {
return [err, [stdout, stderr]];
});
exec('my-command')
.then(function(results) {
console.log("stdout is: " + results[0]);
console.log("stderr is: " + results[1]);
});
Useful for functions that return multiple arguments, for example child_process#exec
.
The lead developer of denodeify is Matt Andrews at FT Labs with much help and support from Kornel Lesiński. All open source code released by FT Labs is licenced under the MIT licence. We welcome comments, feedback and suggestions. Please feel free to raise an issue or pull request.
v1.2.1
denodeify
in internal codeFAQs
Tool to turn functions with Node-style callback APIs into functions that return Promises
The npm package denodeify receives a total of 1,700,885 weekly downloads. As such, denodeify popularity was classified as popular.
We found that denodeify demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.