Assert#

Stability: 3 - Locked
The assert module provides a simple set of assertion tests that can be
used to test invariants. The module is intended for internal use by Node.js,
but can be used in application code via require('assert').
However, assert is not a testing framework, and is not intended to be used
as a general purpose assertion library.
The API for the assert module is Locked. This means that there will be no
additions or changes to any of the methods implemented and exposed by
the module.
assert(value[, message])#
Added in: v0.5.9
An alias of assert.ok() .
const assert = require('assert');
assert(true); // OK
assert(1);
// OK
assert(false);
// throws "AssertionError: false == true"
assert(0);
// throws "AssertionError: 0 == true"
assert(false, 'it\'s false');
// throws "AssertionError: it's false"
assert.deepEqual(actual, expected[, message])#
Added in: v0.1.21
Tests for deep equality between the actual and expected parameters.
Primitive values are compared with the equal comparison operator ( == ).
Only enumerable "own" properties are considered.
The deepEqual() implementation does not test object prototypes, attached
symbols, or non-enumerable properties. This can lead to some potentially
surprising results. For example, the following example does not throw
an AssertionError because the properties on the Error object are nonenumerable:
// WARNING: This does not throw an AssertionError!
assert.deepEqual(Error('a'), Error('b'));
"Deep" equality means that the enumerable "own" properties of child
objects are evaluated also:

const assert = require('assert');

const obj1
a:{
b:1
}
};
const obj2
a:{
b:2
}
};
const obj3
a:{
b:1
}
}
const obj4

={

={

={

= Object.create(obj1);

assert.deepEqual(obj1, obj1);
// OK, object is equal to itself
assert.deepEqual(obj1, obj2);
// AssertionError: { a: { b: 1 } } deepEqual { a: { b: 2 } }
// values of b are different
assert.deepEqual(obj1, obj3);
// OK, objects are equal
assert.deepEqual(obj1, obj4);
// AssertionError: { a: { b: 1 } } deepEqual {}
// Prototypes are ignored
If the values are not equal, an AssertionError is thrown with
a message property set equal to the value of the message parameter. If
the message parameter is undefined, a default error message is assigned.
assert.deepStrictEqual(actual, expected[, message])#
Added in: v1.2.0

Generally identical to assert.deepEqual() with two exceptions. First,

primitive values are compared using the strict equality operator ( === ).
Second, object comparisons include a strict equality check of their
prototypes.
const assert = require('assert');
assert.deepEqual({a:1}, {a:'1'});
// OK, because 1 == '1'
assert.deepStrictEqual({a:1}, {a:'1'});
// AssertionError: { a: 1 } deepStrictEqual { a: '1' }
// because 1 !== '1' using strict equality
If the values are not equal, an AssertionError is thrown with
a message property set equal to the value of the message parameter. If
the message parameter is undefined, a default error message is assigned.
assert.doesNotThrow(block[, error][, message])#
Added in: v0.1.21
Asserts that the function block does not throw an error.
See assert.throws() for more details.
When assert.doesNotThrow() is called, it will immediately call
the block function.
If an error is thrown and it is the same type as that specified by
the error parameter, then an AssertionError is thrown. If the error is of a
different type, or if the error parameter is undefined, the error is
propagated back to the caller.
The following, for instance, will throw the TypeError because there is no
matching error type in the assertion:
assert.doesNotThrow(
() => {
throw new TypeError('Wrong value');
},
SyntaxError
);
However, the following will result in an AssertionError with the message
'Got unwanted exception (TypeError)..':
assert.doesNotThrow(
() => {
throw new TypeError('Wrong value');

},
TypeError
);
If an AssertionError is thrown and a value is provided for
the message parameter, the value of message will be appended to
theAssertionError message:
assert.doesNotThrow(
() => {
throw new TypeError('Wrong value');
},
TypeError,
'Whoops'
);
// Throws: AssertionError: Got unwanted exception (TypeError).
Whoops
assert.equal(actual, expected[, message])#
Added in: v0.1.21
Tests shallow, coercive equality between
the actual and expected parameters using the equal comparison operator
( == ).
const assert = require('assert');
assert.equal(1, 1);
// OK, 1 == 1
assert.equal(1, '1');
// OK, 1 == '1'
assert.equal(1, 2);
// AssertionError: 1 == 2
assert.equal({a: {b: 1}}, {a: {b: 1}});
//AssertionError: { a: { b: 1 } } == { a: { b: 1 } }
If the values are not equal, an AssertionError is thrown with
a message property set equal to the value of the message parameter. If
the message parameter is undefined, a default error message is assigned.
assert.fail(actual, expected, message, operator)#
Added in: v0.1.21

Throws an AssertionError. If message is falsy, the error message is set as

the values of actual and expected separated by the provided operator.
Otherwise, the error message is the value of message.
const assert = require('assert');
assert.fail(1, 2, undefined, '>');
// AssertionError: 1 > 2
assert.fail(1, 2, 'whoops', '>');
// AssertionError: whoops
assert.ifError(value)#
Added in: v0.1.97
Throws value if value is truthy. This is useful when testing
the error argument in callbacks.
const assert = require('assert');
assert.ifError(0); // OK
assert.ifError(1); // Throws 1
assert.ifError('error') // Throws 'error'
assert.ifError(new Error()); // Throws Error
assert.notDeepEqual(actual, expected[, message])#
Added in: v0.1.21
Tests for any deep inequality. Opposite of assert.deepEqual().
const assert = require('assert');
const obj1 = {
a:{
b:1
}
};
const obj2 = {
a:{
b:2
}
};
const obj3 = {
a:{
b:1

}
}
const obj4 = Object.create(obj1);
assert.notDeepEqual(obj1, obj1);
// AssertionError: { a: { b: 1 } } notDeepEqual { a: { b: 1 } }
assert.notDeepEqual(obj1, obj2);
// OK, obj1 and obj2 are not deeply equal
assert.notDeepEqual(obj1, obj3);
// AssertionError: { a: { b: 1 } } notDeepEqual { a: { b: 1 } }
assert.notDeepEqual(obj1, obj4);
// OK, obj1 and obj2 are not deeply equal
If the values are deeply equal, an AssertionError is thrown with
a message property set equal to the value of the message parameter. If
the message parameter is undefined, a default error message is assigned.
assert.notDeepStrictEqual(actual, expected[, message])#
Added in: v1.2.0
Tests for deep strict inequality. Opposite of assert.deepStrictEqual().
const assert = require('assert');
assert.notDeepEqual({a:1}, {a:'1'});
// AssertionError: { a: 1 } notDeepEqual { a: '1' }
assert.notDeepStrictEqual({a:1}, {a:'1'});
// OK
If the values are deeply and strictly equal, an AssertionError is thrown with
a message property set equal to the value of themessage parameter. If
the message parameter is undefined, a default error message is assigned.
assert.notEqual(actual, expected[, message])#
Added in: v0.1.21
Tests shallow, coercive inequality with the not equal comparison operator
( != ).
const assert = require('assert');
assert.notEqual(1, 2);

// OK
assert.notEqual(1, 1);
// AssertionError: 1 != 1
assert.notEqual(1, '1');
// AssertionError: 1 != '1'
If the values are equal, an AssertionError is thrown with
a message property set equal to the value of the message parameter. If
themessage parameter is undefined, a default error message is assigned.
assert.notStrictEqual(actual, expected[, message])#
Added in: v0.1.21
Tests strict inequality as determined by the strict not equal operator ( !
== ).
const assert = require('assert');
assert.notStrictEqual(1, 2);
// OK
assert.notStrictEqual(1, 1);
// AssertionError: 1 != 1
assert.notStrictEqual(1, '1');
// OK
If the values are strictly equal, an AssertionError is thrown with
a message property set equal to the value of the messageparameter. If
the message parameter is undefined, a default error message is assigned.
assert.ok(value[, message])#
Added in: v0.1.21
Tests if value is truthy. It is equivalent to assert.equal(!!value, true,
message).
If value is not truthy, an AssertionError is thrown with a message property
set equal to the value of the message parameter. If
themessage parameter is undefined, a default error message is assigned.
const assert = require('assert');
assert.ok(true); // OK
assert.ok(1);
// OK

assert.ok(false);
// throws "AssertionError: false == true"
assert.ok(0);
// throws "AssertionError: 0 == true"
assert.ok(false, 'it\'s false');
// throws "AssertionError: it's false"
assert.strictEqual(actual, expected[, message])#
Added in: v0.1.21
Tests strict equality as determined by the strict equality operator ( === ).
const assert = require('assert');
assert.strictEqual(1, 2);
// AssertionError: 1 === 2
assert.strictEqual(1, 1);
// OK
assert.strictEqual(1, '1');
// AssertionError: 1 === '1'
If the values are not strictly equal, an AssertionError is thrown with
a message property set equal to the value of the messageparameter. If
the message parameter is undefined, a default error message is assigned.
assert.throws(block[, error][, message])#
Added in: v0.1.21
Expects the function block to throw an error.
If specified, error can be a constructor, RegExp, or validation function.
If specified, message will be the message provided by the AssertionError if
the block fails to throw.
Validate instanceof using constructor:
assert.throws(
() => {
throw new Error('Wrong value');
},
Error
);
Validate error message using RegExp:
assert.throws(

() => {
throw new Error('Wrong value');
},
/value/
);
Custom error validation:
assert.throws(
() => {
throw new Error('Wrong value');
},
function(err) {
if ( (err instanceof Error) && /value/.test(err) ) {
return true;
}
},
'unexpected error'
);
Note that error can not be a string. If a string is provided as the second
argument, then error is assumed to be omitted and the string will be used
for message instead. This can lead to easy-to-miss mistakes:
// THIS IS A MISTAKE! DO NOT DO THIS!
assert.throws(myFunction, 'missing foo', 'did not throw with expected
message');
// Do this instead.
assert.throws(myFunction, /missing foo/, 'did not throw with expected
message');

Buffer

Buffer.from(), Buffer.alloc(), and Buffer.allocUnsafe()

The --zero-fill-buffers command line option

What
makes Buffer.allocUnsafe(size) and Buffer.allocUnsafeSlow(size
) "unsafe"?
Buffers and Character Encodings

Buffers and TypedArray

Buffers and ES6 iteration

Class: Buffer

new Buffer(array)

new Buffer(buffer)

new Buffer(arrayBuffer[, byteOffset [, length]])

new Buffer(size)

new Buffer(str[, encoding])

Class Method: Buffer.alloc(size[, fill[, encoding]])

Class Method: Buffer.allocUnsafe(size)

Class Method: Buffer.allocUnsafeSlow(size)

Class Method: Buffer.byteLength(string[, encoding])

Class Method: Buffer.compare(buf1, buf2)

Class Method: Buffer.concat(list[, totalLength])

Class Method: Buffer.from(array)

Class Method: Buffer.from(arrayBuffer[, byteOffset[,

length]])

Class Method: Buffer.from(buffer)

Class Method: Buffer.from(str[, encoding])

Class Method: Buffer.isBuffer(obj)

Class Method: Buffer.isEncoding(encoding)

buf[index]

buf.compare(target[, targetStart[, targetEnd[,

sourceStart[, sourceEnd]]]])

buf.copy(targetBuffer[, targetStart[, sourceStart[,

sourceEnd]]])

buf.entries()

buf.equals(otherBuffer)

buf.fill(value[, offset[, end]][, encoding])

buf.indexOf(value[, byteOffset][, encoding])

buf.includes(value[, byteOffset][, encoding])

buf.keys()

buf.lastIndexOf(value[, byteOffset][, encoding])

buf.length

buf.readDoubleBE(offset[, noAssert])

buf.readDoubleLE(offset[, noAssert])

buf.readFloatBE(offset[, noAssert])

buf.readFloatLE(offset[, noAssert])

buf.readInt8(offset[, noAssert])

buf.readInt16BE(offset[, noAssert])

buf.readInt16LE(offset[, noAssert])

buf.readInt32BE(offset[, noAssert])

buf.readInt32LE(offset[, noAssert])

buf.readIntBE(offset, byteLength[, noAssert])

buf.readIntLE(offset, byteLength[, noAssert])

buf.readUInt8(offset[, noAssert])

buf.readUInt16BE(offset[, noAssert])

buf.readUInt16LE(offset[, noAssert])

buf.readUInt32BE(offset[, noAssert])

buf.readUInt32LE(offset[, noAssert])

buf.readUIntBE(offset, byteLength[, noAssert])

buf.readUIntLE(offset, byteLength[, noAssert])

buf.slice([start[, end]])

buf.swap16()

buf.swap32()

buf.toString([encoding[, start[, end]]])

buf.toJSON()

buf.values()

buf.write(string[, offset[, length]][, encoding])

buf.writeDoubleBE(value, offset[, noAssert])

buf.writeDoubleLE(value, offset[, noAssert])

buf.writeFloatBE(value, offset[, noAssert])

buf.writeFloatLE(value, offset[, noAssert])

buf.writeInt8(value, offset[, noAssert])

buf.writeInt16BE(value, offset[, noAssert])

buf.writeInt16LE(value, offset[, noAssert])

buf.writeInt32BE(value, offset[, noAssert])

buf.writeInt32LE(value, offset[, noAssert])

buf.writeIntBE(value, offset, byteLength[, noAssert])

buf.writeIntLE(value, offset, byteLength[, noAssert])

buf.writeUInt8(value, offset[, noAssert])

buf.writeUInt16BE(value, offset[, noAssert])

buf.writeUInt16LE(value, offset[, noAssert])

buf.writeUInt32BE(value, offset[, noAssert])

buf.writeUInt32LE(value, offset[, noAssert])

buf.writeUIntBE(value, offset, byteLength[, noAssert])

buf.writeUIntLE(value, offset, byteLength[, noAssert])

buffer.INSPECT_MAX_BYTES

Class: SlowBuffer

new SlowBuffer(size)

Buffer#
Stability: 2 - Stable
Prior to the introduction of TypedArray in ECMAScript 2015 (ES6), the
JavaScript language had no mechanism for reading or manipulating
streams of binary data. The Buffer class was introduced as part of the
Node.js API to make it possible to interact with octet streams in the
context of things like TCP streams and file system operations.
Now that TypedArray has been added in ES6, the Buffer class implements
the Uint8Array API in a manner that is more optimized and suitable for
Node.js' use cases.
Instances of the Buffer class are similar to arrays of integers but
correspond to fixed-sized, raw memory allocations outside the V8 heap.
The size of the Buffer is established when it is created and cannot be
resized.
The Buffer class is a global within Node.js, making it unlikely that one
would need to ever use require('buffer').
const buf1 = Buffer.alloc(10);
// Creates a zero-filled Buffer of length 10.
const buf2 = Buffer.alloc(10, 1);
// Creates a Buffer of length 10, filled with 0x01.
const buf3 = Buffer.allocUnsafe(10);
// Creates an uninitialized buffer of length 10.
// This is faster than calling Buffer.alloc() but the returned

// Buffer instance might contain old data that needs to be

// overwritten using either fill() or write().
const buf4 = Buffer.from([1,2,3]);
// Creates a Buffer containing [01, 02, 03].
const buf5 = Buffer.from('test');
// Creates a Buffer containing ASCII bytes [74, 65, 73, 74].
const buf6 = Buffer.from('tst', 'utf8');
// Creates a Buffer containing UTF8 bytes [74, c3, a9, 73, 74].
Buffer.from(), Buffer.alloc(), and Buffer.allocUnsafe()#
In versions of Node.js prior to v6, Buffer instances were created using
the Buffer constructor function, which allocates the
returnedBuffer differently based on what arguments are provided:

Passing a number as the first argument to Buffer() (e.g. new

Buffer(10)), allocates a new Buffer object of the specified size. The
memory allocated for such Buffer instances is not initialized and can
contain sensitive data. Such Buffer objects must be
initialized manually by using either buf.fill(0) or by writing to
the Buffer completely. While this behavior is intentional to improve
performance, development experience has demonstrated that a more
explicit distinction is required between creating a fast-butuninitialized Buffer versus creating a slower-but-safer Buffer.

Passing a string, array, or Buffer as the first argument copies the

passed object's data into the Buffer.

Passing an ArrayBuffer returns a Buffer that shares allocated

memory with the given ArrayBuffer.

Because the behavior of new Buffer() changes significantly based on the

type of value passed as the first argument, applications that do not
properly validate the input arguments passed to new Buffer(), or that fail
to appropriately initialize newly allocated Buffercontent, can inadvertently
introduce security and reliability issues into their code.
To make the creation of Buffer objects more reliable and less error prone,
the various forms of the new Buffer() constructor have

been deprecated and replaced by separate Buffer.from(), Buffer.alloc(),

and Buffer.allocUnsafe() methods.
Developers should migrate all existing uses of the new
Buffer() constructors to one of these new APIs.

Buffer.from(array) returns a new Buffer containing a copy of the

provided octets.

Buffer.from(arrayBuffer[, byteOffset [, length]]) returns a

new Buffer that shares the same allocated memory as the
given ArrayBuffer.

Buffer.from(buffer) returns a new Buffer containing a copy of the

contents of the given Buffer.

Buffer.from(str[, encoding]) returns a new Buffer containing

a copy of the provided string.

Buffer.alloc(size[, fill[, encoding]]) returns a "filled" Buffer instance

of the specified size. This method can be significantly slower
than Buffer.allocUnsafe(size) but ensures that newly
created Buffer instances never contain old and potentially sensitive
data.

Buffer.allocUnsafe(size) and Buffer.allocUnsafeSlow(size) each return

a new Buffer of the specified size whose contentmust be initialized
using either buf.fill(0) or written to completely.

Buffer instances returned by Buffer.allocUnsafe(size) may be allocated off

a shared internal memory pool if size is less than or equal to
half Buffer.poolSize. Instances returned
by Buffer.allocUnsafeSlow(size) never use the shared internal memory
pool.
The --zero-fill-buffers command line option#
Added in: v5.10.0
Node.js can be started using the --zero-fill-buffers command line option to
force all newly allocated Buffer instances created using either new
Buffer(size), Buffer.allocUnsafe(size), Buffer.allocUnsafeSlow(size) or new
SlowBuffer(size) to beautomatically zero-filled upon creation. Use of this
flag changes the default behavior of these methods and can have a
significant impact on performance. Use of the --zero-fill-buffers option is

recommended only when absolutely necessary to enforce that newly

allocated Buffer instances cannot contain potentially sensitive data.
$ node --zero-fill-buffers
> Buffer.allocUnsafe(5);
<Buffer 00 00 00 00 00>
What
makes Buffer.allocUnsafe(size) and Buffer.allocUnsafeSlow(size) "
unsafe"?#
When calling Buffer.allocUnsafe() (and Buffer.allocUnsafeSlow()), the
segment of allocated memory is uninitialized (it is not zeroed-out). While
this design makes the allocation of memory quite fast, the allocated
segment of memory might contain old data that is potentially sensitive.
Using a Buffer created
by Buffer.allocUnsafe() without completely overwriting the memory can
allow this old data to be leaked when the Buffer memory is read.
While there are clear performance advantages to
using Buffer.allocUnsafe(), extra care must be taken in order to avoid
introducing security vulnerabilities into an application.
Buffers and Character Encodings#
Buffers are commonly used to represent sequences of encoded characters
such as UTF8, UCS2, Base64 or even Hex-encoded data. It is possible to
convert back and forth between Buffers and ordinary JavaScript string
objects by using an explicit encoding method.
const buf = Buffer.from('hello world', 'ascii');
console.log(buf.toString('hex'));
// prints: 68656c6c6f20776f726c64
console.log(buf.toString('base64'));
// prints: aGVsbG8gd29ybGQ=
The character encodings currently supported by Node.js include:

'ascii' - for 7-bit ASCII data only. This encoding method is very fast
and will strip the high bit if set.

'utf8' - Multibyte encoded Unicode characters. Many web pages and

other document formats use UTF-8.

'utf16le' - 2 or 4 bytes, little-endian encoded Unicode characters.

Surrogate pairs (U+10000 to U+10FFFF) are supported.

'ucs2' - Alias of 'utf16le'.

'base64' - Base64 string encoding. When creating a buffer from a

string, this encoding will also correctly accept "URL and Filename Safe
Alphabet" as specified in RFC 4648, Section 5.

'binary' - A way of encoding the buffer into a one-byte (latin-1)

encoded string. The string 'latin-1' is not supported. Instead,
pass 'binary' to use 'latin-1' encoding.

'hex' - Encode each byte as two hexadecimal characters.

Buffers and TypedArray#

Buffers are also Uint8Array TypedArray instances. However, there are
subtle incompatibilities with the TypedArray specification in ECMAScript
2015. For instance, while ArrayBuffer#slice() creates a copy of the slice,
the implementation of Buffer#slice()creates a view over the existing
Buffer without copying, making Buffer#slice() far more efficient.
It is also possible to create new TypedArray instances from a Buffer with
the following caveats:
1.

The Buffer object's memory is copied to the TypedArray, not shared.

2.

The Buffer object's memory is interpreted as an array of distinct

elements, and not as a byte array of the target type. That is, new
Uint32Array(Buffer.from([1,2,3,4])) creates a 4element Uint32Array with elements [1,2,3,4], not a Uint32Array with a
single element [0x1020304] or [0x4030201].

It is possible to create a new Buffer that shares the same allocated

memory as a TypedArray instance by using the TypeArray
object's.buffer property:

const arr = new Uint16Array(2);

arr[0] = 5000;
arr[1] = 4000;
const buf1 = Buffer.from(arr); // copies the buffer
const buf2 = Buffer.from(arr.buffer); // shares the memory with arr;
console.log(buf1);
// Prints: <Buffer 88 a0>, copied buffer has only two elements
console.log(buf2);
// Prints: <Buffer 88 13 a0 0f>
arr[1] = 6000;
console.log(buf1);
// Prints: <Buffer 88 a0>
console.log(buf2);
// Prints: <Buffer 88 13 70 17>
Note that when creating a Buffer using the TypedArray's .buffer, it is
possible to use only a portion of the underlying ArrayBufferby passing
in byteOffset and length parameters:
const arr = new Uint16Array(20);
const buf = Buffer.from(arr.buffer, 0, 16);
console.log(buf.length);
// Prints: 16
The Buffer.from() and TypedArray.from() (e.g.Uint8Array.from()) have
different signatures and implementations. Specifically, the TypedArray
variants accept a second argument that is a mapping function that is
invoked on every element of the typed array:

TypedArray.from(source[, mapFn[, thisArg]])

The Buffer.from() method, however, does not support the use of a

mapping function:

Buffer.from(array)

Buffer.from(buffer)

Buffer.from(arrayBuffer[, byteOffset [, length]])

Buffer.from(str[, encoding])

Buffers and ES6 iteration#

Buffers can be iterated over using the ECMAScript 2015
(ES6) for..of syntax:
const buf = Buffer.from([1, 2, 3]);
for (var b of buf)
console.log(b)
//
//
//
//

Prints:
1
2
3

Additionally, the buf.values(), buf.keys(), and buf.entries() methods can be

used to create iterators.
Class: Buffer#
The Buffer class is a global type for dealing with binary data directly. It can
be constructed in a variety of ways.
new Buffer(array)#
Deprecated since: v6.0.0
Stability: 0 - Deprecated: Use Buffer.from(array)
instead.

array <Array>

Allocates a new Buffer using an array of octets.

const buf = new Buffer([0x62,0x75,0x66,0x66,0x65,0x72]);
// creates a new Buffer containing ASCII bytes
// ['b','u','f','f','e','r']
new Buffer(buffer)#
Deprecated since: v6.0.0

Stability: 0 - Deprecated: Use Buffer.from(buffer)

instead.

buffer <Buffer>

Copies the passed buffer data onto a new Buffer instance.

const buf1 = new Buffer('buffer');
const buf2 = new Buffer(buf1);
buf1[0] = 0x61;
console.log(buf1.toString());
// 'auffer'
console.log(buf2.toString());
// 'buffer' (copy is not changed)
new Buffer(arrayBuffer[, byteOffset [, length]])#
Deprecated since: v6.0.0
Stability: 0 - Deprecated: Use
Buffer.from(arrayBuffer[, byteOffset [, length]])
instead.

arrayBuffer <ArrayBuffer> The .buffer property of a TypedArray or

a new ArrayBuffer()

byteOffset <Number> Default: 0

length <Number> Default: arrayBuffer.length - byteOffset

When passed a reference to the .buffer property of a TypedArray instance,

the newly created Buffer will share the same allocated memory as the
TypedArray.
The optional byteOffset and length arguments specify a memory range
within the arrayBuffer that will be shared by the Buffer.
const arr = new Uint16Array(2);
arr[0] = 5000;
arr[1] = 4000;
const buf = new Buffer(arr.buffer); // shares the memory with arr;

console.log(buf);
// Prints: <Buffer 88 13 a0 0f>
// changing the TypdArray changes the Buffer also
arr[1] = 6000;
console.log(buf);
// Prints: <Buffer 88 13 70 17>
new Buffer(size)#
Deprecated since: v6.0.0
Stability: 0 - Deprecated: Use
Buffer.alloc(size[, fill[, encoding]]) instead (also
see Buffer.allocUnsafe(size)).

size <Number>

Allocates a new Buffer of size bytes. The size must be less than or equal to
the value of require('buffer').kMaxLength (on 64-bit
architectures, kMaxLength is (2^31)-1). Otherwise, a RangeError is
thrown. A zero-length Buffer will be created if a size less than or equal to 0
is specified.
Unlike ArrayBuffers, the underlying memory for Buffer instances created in
this way is not initialized. The contents of a newly created Buffer are
unknown and could contain sensitive data. Use buf.fill(0) to initialize
a Buffer to zeroes.
const buf = new Buffer(5);
console.log(buf);
// <Buffer 78 e0 82 02 01>
// (octets will be different, every time)
buf.fill(0);
console.log(buf);
// <Buffer 00 00 00 00 00>
new Buffer(str[, encoding])#
Deprecated since: v6.0.0
Stability: 0 - Deprecated:

Use Buffer.from(str[, encoding]) instead.

str <String> string to encode.

encoding <String> Default: 'utf8'

Creates a new Buffer containing the given JavaScript string str. If provided,
the encoding parameter identifies the strings character encoding.
const buf1 = new Buffer('this is a tst');
console.log(buf1.toString());
// prints: this is a tst
console.log(buf1.toString('ascii'));
// prints: this is a tC)st
const buf2 = new Buffer('7468697320697320612074c3a97374',
'hex');
console.log(buf2.toString());
// prints: this is a tst
Class Method: Buffer.alloc(size[, fill[, encoding]])#
Added in: v5.10.0

size <Number>

fill <Value> Default: undefined

encoding <String> Default: utf8

Allocates a new Buffer of size bytes. If fill is undefined, the Buffer will
be zero-filled.
const buf = Buffer.alloc(5);
console.log(buf);
// <Buffer 00 00 00 00 00>
The size must be less than or equal to the value
of require('buffer').kMaxLength (on 64-bit
architectures, kMaxLength is(2^31)-1). Otherwise, a RangeError is thrown.
A zero-length Buffer will be created if a size less than or equal to 0 is
specified.

If fill is specified, the allocated Buffer will be initialized by

calling buf.fill(fill). See buf.fill() for more information.
const buf = Buffer.alloc(5, 'a');
console.log(buf);
// <Buffer 61 61 61 61 61>
If both fill and encoding are specified, the allocated Buffer will be
initialized by calling buf.fill(fill, encoding). For example:
const buf = Buffer.alloc(11, 'aGVsbG8gd29ybGQ=', 'base64');
console.log(buf);
// <Buffer 68 65 6c 6c 6f 20 77 6f 72 6c 64>
Calling Buffer.alloc(size) can be significantly slower than the
alternative Buffer.allocUnsafe(size) but ensures that the newly
created Buffer instance contents will never contain sensitive data.
A TypeError will be thrown if size is not a number.
Class Method: Buffer.allocUnsafe(size)#
Added in: v5.10.0

size <Number>

Allocates a new non-zero-filled Buffer of size bytes. The size must be less
than or equal to the value ofrequire('buffer').kMaxLength (on 64-bit
architectures, kMaxLength is (2^31)-1). Otherwise, a RangeError is
thrown. A zero-length Buffer will be created if a size less than or equal to 0
is specified.
The underlying memory for Buffer instances created in this way is not
initialized. The contents of the newly created Buffer are unknown and may
contain sensitive data. Use buf.fill(0) to initialize such Buffer instances to
zeroes.
const buf = Buffer.allocUnsafe(5);
console.log(buf);
// <Buffer 78 e0 82 02 01>
// (octets will be different, every time)
buf.fill(0);

console.log(buf);
// <Buffer 00 00 00 00 00>
A TypeError will be thrown if size is not a number.
Note that the Buffer module pre-allocates an internal Buffer instance of
size Buffer.poolSize that is used as a pool for the fast allocation of
new Buffer instances created using Buffer.allocUnsafe(size) (and the
deprecated new Buffer(size) constructor) only when size is less than or
equal to Buffer.poolSize >> 1 (floor of Buffer.poolSize divided by two). The
default value ofBuffer.poolSize is 8192 but can be modified.
Use of this pre-allocated internal memory pool is a key difference between
calling Buffer.alloc(size, fill) vs.Buffer.allocUnsafe(size).fill(fill).
Specifically, Buffer.alloc(size, fill) will never use the internal Buffer pool,
whileBuffer.allocUnsafe(size).fill(fill) will use the internal Buffer pool
if size is less than or equal to half Buffer.poolSize. The difference is subtle
but can be important when an application requires the additional
performance that Buffer.allocUnsafe(size)provides.
Class Method: Buffer.allocUnsafeSlow(size)#
Added in: v5.10.0

size <Number>

Allocates a new non-zero-filled and non-pooled Buffer of size bytes.

The size must be less than or equal to the value
ofrequire('buffer').kMaxLength (on 64-bit
architectures, kMaxLength is (2^31)-1). Otherwise, a RangeError is
thrown. A zero-length Buffer will be created if a size less than or equal to 0
is specified.
The underlying memory for Buffer instances created in this way is not
initialized. The contents of the newly created Buffer are unknown and may
contain sensitive data. Use buf.fill(0) to initialize such Buffer instances to
zeroes.
When using Buffer.allocUnsafe() to allocate new Buffer instances,
allocations under 4KB are, by default, sliced from a single preallocated Buffer. This allows applications to avoid the garbage collection

overhead of creating many individually allocated Buffers. This approach

improves both performance and memory usage by eliminating the need to
track and cleanup as many Persistentobjects.
However, in the case where a developer may need to retain a small chunk
of memory from a pool for an indeterminate amount of time, it may be
appropriate to create an un-pooled Buffer instance
using Buffer.allocUnsafeSlow() then copy out the relevant bits.
// need to keep around a few small chunks of memory
const store = [];
socket.on('readable', () => {
const data = socket.read();
// allocate for retained data
const sb = Buffer.allocUnsafeSlow(10);
// copy the data into the new allocation
data.copy(sb, 0, 0, 10);
store.push(sb);
});
Use of Buffer.allocUnsafeSlow() should be used only as a last resort after a
developer has observed undue memory retention in their applications.
A TypeError will be thrown if size is not a number.
Class Method: Buffer.byteLength(string[, encoding])#

string <String> | <Buffer> | <TypedArray> | <DataView> | <ArrayB

uffer>

encoding <String> Default: 'utf8'

Return: <Number>

Returns the actual byte length of a string. This is not the same
as String.prototype.length since that returns the number of charactersin a
string.
Example:

const str = '\u00bd + \u00bc = \u00be';

console.log(`${str}: ${str.length} characters, ` +
`${Buffer.byteLength(str, 'utf8')} bytes`);
// + = : 9 characters, 12 bytes
When string is a Buffer/DataView/TypedArray/ArrayBuffer, returns the
actual byte length.
Otherwise, converts to String and returns the byte length of string.
Class Method: Buffer.compare(buf1, buf2)#
Added in: v0.11.13

buf1 <Buffer>

buf2 <Buffer>

Return: <Number>

Compares buf1 to buf2 typically for the purpose of sorting arrays of

Buffers. This is equivalent is calling buf1.compare(buf2).
const arr = [Buffer.from('1234'), Buffer.from('0123')];
arr.sort(Buffer.compare);
Class Method: Buffer.concat(list[, totalLength])#
Added in: v0.7.11

list <Array> List of Buffer objects to concat

totalLength <Number> Total length of the Buffers in the list when
concatenated
Return: <Buffer>

Returns a new Buffer which is the result of concatenating all the Buffers in
the list together.
If the list has no items, or if the totalLength is 0, then a new zero-length
Buffer is returned.

If totalLength is not provided, it is calculated from the Buffers in the list.

This, however, adds an additional loop to the function, so it is faster to
provide the length explicitly.
Example: build a single Buffer from a list of three Buffers:
const
const
const
const

buf1 = Buffer.alloc(10);
buf2 = Buffer.alloc(14);
buf3 = Buffer.alloc(18);
totalLength = buf1.length + buf2.length + buf3.length;

console.log(totalLength);
const bufA = Buffer.concat([buf1, buf2, buf3], totalLength);
console.log(bufA);
console.log(bufA.length);
// 42
// <Buffer 00 00 00 00 ...>
// 42
Class Method: Buffer.from(array)#
Added in: v3.0.0

array <Array>

Allocates a new Buffer using an array of octets.

const buf = Buffer.from([0x62,0x75,0x66,0x66,0x65,0x72]);
// creates a new Buffer containing ASCII bytes
// ['b','u','f','f','e','r']
A TypeError will be thrown if array is not an Array.
Class Method: Buffer.from(arrayBuffer[, byteOffset[, length]])#
Added in: v5.10.0

arrayBuffer <ArrayBuffer> The .buffer property of a TypedArray or

a new ArrayBuffer()

byteOffset <Number> Default: 0

length <Number> Default: arrayBuffer.length - byteOffset

When passed a reference to the .buffer property of a TypedArray instance,

the newly created Buffer will share the same allocated memory as the
TypedArray.
const arr = new Uint16Array(2);
arr[0] = 5000;
arr[1] = 4000;
const buf = Buffer.from(arr.buffer); // shares the memory with arr;
console.log(buf);
// Prints: <Buffer 88 13 a0 0f>
// changing the TypedArray changes the Buffer also
arr[1] = 6000;
console.log(buf);
// Prints: <Buffer 88 13 70 17>
The optional byteOffset and length arguments specify a memory range
within the arrayBuffer that will be shared by the Buffer.
const ab = new ArrayBuffer(10);
const buf = Buffer.from(ab, 0, 2);
console.log(buf.length);
// Prints: 2
A TypeError will be thrown if arrayBuffer is not an ArrayBuffer.
Class Method: Buffer.from(buffer)#
Added in: v3.0.0

buffer <Buffer>

Copies the passed buffer data onto a new Buffer instance.

const buf1 = Buffer.from('buffer');
const buf2 = Buffer.from(buf1);
buf1[0] = 0x61;

console.log(buf1.toString());
// 'auffer'
console.log(buf2.toString());
// 'buffer' (copy is not changed)
A TypeError will be thrown if buffer is not a Buffer.
Class Method: Buffer.from(str[, encoding])#
Added in: v5.10.0

str <String> String to encode.

encoding <String> Encoding to use, Default: 'utf8'

Creates a new Buffer containing the given JavaScript string str. If provided,
the encoding parameter identifies the character encoding. If not
provided, encoding defaults to 'utf8'.
const buf1 = Buffer.from('this is a tst');
console.log(buf1.toString());
// prints: this is a tst
console.log(buf1.toString('ascii'));
// prints: this is a tC)st
const buf2 = Buffer.from('7468697320697320612074c3a97374',
'hex');
console.log(buf2.toString());
// prints: this is a tst
A TypeError will be thrown if str is not a string.
Class Method: Buffer.isBuffer(obj)#

obj <Object>

Return: <Boolean>

Returns 'true' if obj is a Buffer.

Class Method: Buffer.isEncoding(encoding)#
Added in: v0.9.1

encoding <String> The encoding string to test

Return: <Boolean>

Returns true if the encoding is a valid encoding argument, or false

otherwise.
buf[index]#
The index operator [index] can be used to get and set the octet at
position index in the Buffer. The values refer to individual bytes, so the
legal value range is between 0x00 and 0xFF (hex) or 0 and 255 (decimal).
Example: copy an ASCII string into a Buffer, one byte at a time:
const str = "Node.js";
const buf = Buffer.allocUnsafe(str.length);
for (let i = 0; i < str.length ; i++) {
buf[i] = str.charCodeAt(i);
}
console.log(buf.toString('ascii'));
// Prints: Node.js
buf.compare(target[, targetStart[, targetEnd[, sourceStart[,
sourceEnd]]]])#
Added in: v0.11.13

target <Buffer>

targetStart <Integer> The offset within target at which to begin

comparison. default = 0.

targetEnd <Integer> The offset with target at which to end

comparison. Ignored when targetStart is undefined. default
=target.byteLength.

sourceStart <Integer> The offset within buf at which to begin

comparison. Ignored when targetStart is undefined. default =0

sourceEnd <Integer> The offset within buf at which to end

comparison. Ignored when targetStart is undefined. default
=buf.byteLength.

Return: <Number>

Compares two Buffer instances and returns a number indicating

whether buf comes before, after, or is the same as the target in sort order.
Comparison is based on the actual sequence of bytes in each Buffer.

0 is returned if target is the same as buf

1 is returned if target should come before buf when sorted.

-1 is returned if target should come after buf when sorted.

const buf1 = Buffer.from('ABC');
const buf2 = Buffer.from('BCD');
const buf3 = Buffer.from('ABCD');
console.log(buf1.compare(buf1));
// Prints: 0
console.log(buf1.compare(buf2));
// Prints: -1
console.log(buf1.compare(buf3));
// Prints: 1
console.log(buf2.compare(buf1));
// Prints: 1
console.log(buf2.compare(buf3));
// Prints: 1
[buf1, buf2, buf3].sort(Buffer.compare);
// produces sort order [buf1, buf3, buf2]

The optional targetStart, targetEnd, sourceStart,

and sourceEnd arguments can be used to limit the comparison to specific
ranges within the two Buffer objects.
const buf1 = Buffer.from([1, 2, 3, 4, 5, 6, 7, 8, 9]);
const buf2 = Buffer.from([5, 6, 7, 8, 9, 1, 2, 3, 4]);
console.log(buf1.compare(buf2, 5, 9, 0, 4));
// Prints: 0
console.log(buf1.compare(buf2, 0, 6, 4));
// Prints: -1

console.log(buf1.compare(buf2, 5, 6, 5));
// Prints: 1
A RangeError will be thrown if: targetStart < 0, sourceStart < 0, targetEnd
> target.byteLength or sourceEnd > source.byteLength.
buf.copy(targetBuffer[, targetStart[, sourceStart[, sourceEnd]]])#

targetBuffer <Buffer> Buffer to copy into

targetStart <Number> Default: 0

sourceStart <Number> Default: 0

sourceEnd <Number> Default: buffer.length

Return: <Number> The number of bytes copied.

Copies data from a region of this Buffer to a region in the target Buffer
even if the target memory region overlaps with the source.
Example: build two Buffers, then copy buf1 from byte 16 through byte 19
into buf2, starting at the 8th byte in buf2.
const buf1 = Buffer.allocUnsafe(26);
const buf2 = Buffer.allocUnsafe(26).fill('!');
for (let i = 0 ; i < 26 ; i++) {
buf1[i] = i + 97; // 97 is ASCII a
}
buf1.copy(buf2, 8, 16, 20);
console.log(buf2.toString('ascii', 0, 25));
// Prints: !!!!!!!!qrst!!!!!!!!!!!!!
Example: Build a single Buffer, then copy data from one region to an
overlapping region in the same Buffer
const buf = Buffer.allocUnsafe(26);
for (var i = 0 ; i < 26 ; i++) {
buf[i] = i + 97; // 97 is ASCII a

}
buf.copy(buf, 0, 4, 10);
console.log(buf.toString());
// efghijghijklmnopqrstuvwxyz
buf.entries()#
Added in: v1.1.0

Return: <Iterator>

Creates and returns an iterator of [index, byte] pairs from the Buffer
contents.
const buf = Buffer.from('buffer');
for (var pair of buf.entries()) {
console.log(pair);
}
// prints:
// [0, 98]
// [1, 117]
// [2, 102]
// [3, 102]
// [4, 101]
// [5, 114]
buf.equals(otherBuffer)#
Added in: v1.0.0

otherBuffer <Buffer>

Return: <Boolean>

Returns a boolean indicating whether this and otherBuffer have exactly

the same bytes.
const buf1 = Buffer.from('ABC');
const buf2 = Buffer.from('414243', 'hex');
const buf3 = Buffer.from('ABCD');
console.log(buf1.equals(buf2));
// Prints: true

console.log(buf1.equals(buf3));
// Prints: false
buf.fill(value[, offset[, end]][, encoding])#
Added in: v0.5.0

value <String> | <Buffer> | <Number>

offset <Number> Default: 0

end <Number> Default: buf.length

encoding <String> Default: 'utf8'

Return: <Buffer>

Fills the Buffer with the specified value. If the offset (defaults to 0)
and end (defaults to buf.length) are not given the entire buffer will be
filled. The method returns a reference to the Buffer, so calls can be
chained. This is meant as a small simplification to creating a Buffer.
Allowing the creation and fill of the Buffer to be done on a single line:
const b = Buffer.allocUnsafe(50).fill('h');
console.log(b.toString());
// Prints:
hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhh
encoding is only relevant if value is a string. Otherwise it is
ignored. value is coerced to a uint32 value if it is not a String or Number.
The fill() operation writes bytes into the Buffer dumbly. If the final write
falls in between a multi-byte character then whatever bytes fit into the
buffer are written.
Buffer(3).fill('\u0222');
// Prints: <Buffer c8 a2 c8>
buf.indexOf(value[, byteOffset][, encoding])#
Added in: v1.5.0

value <String> | <Buffer> | <Number>

byteOffset <Number> Default: 0

encoding <String> Default: 'utf8'

Return: <Number>

Operates similar to Array#indexOf() in that it returns either the starting

index position of value in Buffer or -1 if the Buffer does not contain value.
The value can be a String, Buffer or Number. Strings are by default
interpreted as UTF8. Buffers will use the entire Buffer (to compare a
partial Buffer use buf.slice()). Numbers can range from 0 to 255.
const buf = Buffer.from('this is a buffer');
buf.indexOf('this');
// returns 0
buf.indexOf('is');
// returns 2
buf.indexOf(Buffer.from('a buffer'));
// returns 8
buf.indexOf(97); // ascii for 'a'
// returns 8
buf.indexOf(Buffer.from('a buffer example'));
// returns -1
buf.indexOf(Buffer.from('a buffer example').slice(0,8));
// returns 8
const utf16Buffer = Buffer.from('\u039a\u0391\u03a3\u03a3\u0395',
'ucs2');
utf16Buffer.indexOf('\u03a3', 0, 'ucs2');
// returns 4
utf16Buffer.indexOf('\u03a3', -4, 'ucs2');
// returns 6
buf.includes(value[, byteOffset][, encoding])#
Added in: v5.3.0

value <String> | <Buffer> | <Number>

byteOffset <Number> Default: 0

encoding <String> Default: 'utf8'

Return: <Boolean>

Operates similar to Array#includes(). The value can be a String, Buffer or

Number. Strings are interpreted as UTF8 unless overridden with
the encoding argument. Buffers will use the entire Buffer (to compare a
partial Buffer use buf.slice()). Numbers can range from 0 to 255.
The byteOffset indicates the index in buf where searching begins.
const buf = Buffer.from('this is a buffer');
buf.includes('this');
// returns true
buf.includes('is');
// returns true
buf.includes(Buffer.from('a buffer'));
// returns true
buf.includes(97); // ascii for 'a'
// returns true
buf.includes(Buffer.from('a buffer example'));
// returns false
buf.includes(Buffer.from('a buffer example').slice(0,8));
// returns true
buf.includes('this', 4);
// returns false
buf.keys()#
Added in: v1.1.0

Return: <Iterator>

Creates and returns an iterator of Buffer keys (indices).

const buf = Buffer.from('buffer');
for (var key of buf.keys()) {
console.log(key);
}
// prints:
// 0
// 1
// 2
// 3
// 4

// 5
buf.lastIndexOf(value[, byteOffset][, encoding])#
Added in: v6.0.0

value <String> | <Buffer> | <Number>

byteOffset <Number> Default: buf.length

encoding <String> Default: 'utf8'

Return: <Number>

Identical to Buffer#indexOf(), but searches the Buffer from back to front

instead of front to back. Returns the starting index position of value in
Buffer or -1 if the Buffer does not contain value. The value can be a String,
Buffer or Number. Strings are by default interpreted as UTF8.
If byteOffset is provided, will return the last match that begins at or
before byteOffset.
const buf = new Buffer('this buffer is a buffer');
buf.lastIndexOf('this');
// returns 0
buf.lastIndexOf('buffer');
// returns 17
buf.lastIndexOf(new Buffer('buffer'));
// returns 17
buf.lastIndexOf(97); // ascii for 'a'
// returns 15
buf.lastIndexOf(new Buffer('yolo'));
// returns -1
buf.lastIndexOf('buffer', 5)
// returns 5
buf.lastIndexOf('buffer', 4)
// returns -1
const utf16Buffer = new Buffer('\u039a\u0391\u03a3\u03a3\u0395',
'ucs2');
utf16Buffer.lastIndexOf('\u03a3', null, 'ucs2');

// returns 6
utf16Buffer.lastIndexOf('\u03a3', -5, 'ucs2');
// returns 4
buf.length#

<Number>

Returns the amount of memory allocated for the Buffer in number of

bytes. Note that this does not necessarily reflect the amount of usable
data within the Buffer. For instance, in the example below, a Buffer with
1234 bytes is allocated, but only 11 ASCII bytes are written.
const buf = Buffer.alloc(1234);
console.log(buf.length);
// Prints: 1234
buf.write('some string', 0, 'ascii');
console.log(buf.length);
// Prints: 1234
While the length property is not immutable, changing the value
of length can result in undefined and inconsistent behavior. Applications
that wish to modify the length of a Buffer should therefore treat length as
read-only and use buf.slice() to create a new Buffer.
var buf = Buffer.allocUnsafe(10);
buf.write('abcdefghj', 0, 'ascii');
console.log(buf.length);
// Prints: 10
buf = buf.slice(0,5);
console.log(buf.length);
// Prints: 5
buf.readDoubleBE(offset[, noAssert])#
buf.readDoubleLE(offset[, noAssert])#

offset <Number> 0 <= offset <= buf.length - 8

noAssert <Boolean> Default: false

Return: <Number>

Reads a 64-bit double from the Buffer at the specified offset with specified
endian format (readDoubleBE() returns big endian,readDoubleLE() returns
little endian).
Setting noAssert to true skips validation of the offset. This allows
the offset to be beyond the end of the Buffer.
const buf = Buffer.from([1,2,3,4,5,6,7,8]);
buf.readDoubleBE();
// Returns: 8.20788039913184e-304
buf.readDoubleLE();
// Returns: 5.447603722011605e-270
buf.readDoubleLE(1);
// throws RangeError: Index out of range
buf.readDoubleLE(1, true); // Warning: reads passed end of buffer!
// Segmentation fault! don't do this!
buf.readFloatBE(offset[, noAssert])#
buf.readFloatLE(offset[, noAssert])#

offset <Number> 0 <= offset <= buf.length - 4

noAssert <Boolean> Default: false

Return: <Number>

Reads a 32-bit float from the Buffer at the specified offset with specified
endian format (readFloatBE() returns big endian,readFloatLE() returns little
endian).
Setting noAssert to true skips validation of the offset. This allows
the offset to be beyond the end of the Buffer.
const buf = Buffer.from([1,2,3,4]);
buf.readFloatBE();
// Returns: 2.387939260590663e-38
buf.readFloatLE();
// Returns: 1.539989614439558e-36
buf.readFloatLE(1);

// throws RangeError: Index out of range

buf.readFloatLE(1, true); // Warning: reads passed end of buffer!
// Segmentation fault! don't do this!
buf.readInt8(offset[, noAssert])#

offset <Number> 0 <= offset <= buf.length - 1

noAssert <Boolean> Default: false

Return: <Number>

Reads a signed 8-bit integer from the Buffer at the specified offset.
Setting noAssert to true skips validation of the offset. This allows
the offset to be beyond the end of the Buffer.
Integers read from the Buffer are interpreted as two's complement signed
values.
const buf = Buffer.from([1,-2,3,4]);
buf.readInt8(0);
// returns 1
buf.readInt8(1);
// returns -2
buf.readInt16BE(offset[, noAssert])#
buf.readInt16LE(offset[, noAssert])#

offset <Number> 0 <= offset <= buf.length - 2

noAssert <Boolean> Default: false

Return: <Number>

Reads a signed 16-bit integer from the Buffer at the specified offset with
the specified endian format (readInt16BE() returns big
endian, readInt16LE() returns little endian).
Setting noAssert to true skips validation of the offset. This allows
the offset to be beyond the end of the Buffer.

Integers read from the Buffer are interpreted as two's complement signed
values.
const buf = Buffer.from([1,-2,3,4]);
buf.readInt16BE();
// returns 510
buf.readInt16LE(1);
// returns 1022
buf.readInt32BE(offset[, noAssert])#
buf.readInt32LE(offset[, noAssert])#

offset <Number> 0 <= offset <= buf.length - 4

noAssert <Boolean> Default: false

Return: <Number>

Reads a signed 32-bit integer from the Buffer at the specified offset with
the specified endian format (readInt32BE() returns big
endian, readInt32LE() returns little endian).
Setting noAssert to true skips validation of the offset. This allows
the offset to be beyond the end of the Buffer.
Integers read from the Buffer are interpreted as two's complement signed
values.
const buf = Buffer.from([1,-2,3,4]);
buf.readInt32BE();
// returns 33424132
buf.readInt32LE();
// returns 67370497
buf.readInt32LE(1);
// throws RangeError: Index out of range
buf.readIntBE(offset, byteLength[, noAssert])#
buf.readIntLE(offset, byteLength[, noAssert])#
Added in: v1.0.0

offset <Number> 0 <= offset <= buf.length - byteLength

byteLength <Number> 0 < byteLength <= 6

noAssert <Boolean> Default: false

Return: <Number>

Reads byteLength number of bytes from the Buffer at the

specified offset and interprets the result as a two's complement signed
value. Supports up to 48 bits of accuracy. For example:
const buf = Buffer.allocUnsafe(6);
buf.writeUInt16LE(0x90ab, 0);
buf.writeUInt32LE(0x12345678, 2);
buf.readIntLE(0, 6).toString(16); // Specify 6 bytes (48 bits)
// Returns: '1234567890ab'
buf.readIntBE(0, 6).toString(16);
// Returns: -546f87a9cbee
Setting noAssert to true skips validation of the offset. This allows
the offset to be beyond the end of the Buffer.
buf.readUInt8(offset[, noAssert])#

offset <Number> 0 <= offset <= buf.length - 1

noAssert <Boolean> Default: false

Return: <Number>

Reads an unsigned 8-bit integer from the Buffer at the specified offset.
Setting noAssert to true skips validation of the offset. This allows
the offset to be beyond the end of the Buffer.
const buf = Buffer.from([1,-2,3,4]);
buf.readUInt8(0);
// returns 1
buf.readUInt8(1);
// returns 254

buf.readUInt16BE(offset[, noAssert])#
buf.readUInt16LE(offset[, noAssert])#

offset <Number> 0 <= offset <= buf.length - 2

noAssert <Boolean> Default: false

Return: <Number>

Reads an unsigned 16-bit integer from the Buffer at the

specified offset with specified endian format (readUInt16BE() returns big
endian, readUInt16LE() returns little endian).
Setting noAssert to true skips validation of the offset. This allows
the offset to be beyond the end of the Buffer.
Example:
const buf = Buffer.from([0x3, 0x4, 0x23, 0x42]);
buf.readUInt16BE(0);
// Returns: 0x0304
buf.readUInt16LE(0);
// Returns: 0x0403
buf.readUInt16BE(1);
// Returns: 0x0423
buf.readUInt16LE(1);
// Returns: 0x2304
buf.readUInt16BE(2);
// Returns: 0x2342
buf.readUInt16LE(2);
// Returns: 0x4223
buf.readUInt32BE(offset[, noAssert])#
buf.readUInt32LE(offset[, noAssert])#

offset <Number> 0 <= offset <= buf.length - 4

noAssert <Boolean> Default: false

Return: <Number>

Reads an unsigned 32-bit integer from the Buffer at the

specified offset with specified endian format (readUInt32BE() returns big
endian, readUInt32LE() returns little endian).
Setting noAssert to true skips validation of the offset. This allows
the offset to be beyond the end of the Buffer.
Example:
const buf = Buffer.from([0x3, 0x4, 0x23, 0x42]);
buf.readUInt32BE(0);
// Returns: 0x03042342
console.log(buf.readUInt32LE(0));
// Returns: 0x42230403
buf.readUIntBE(offset, byteLength[, noAssert])#
buf.readUIntLE(offset, byteLength[, noAssert])#
Added in: v1.0.0

offset <Number> 0 <= offset <= buf.length - byteLength

byteLength <Number> 0 < byteLength <= 6

noAssert <Boolean> Default: false

Return: <Number>

Reads byteLength number of bytes from the Buffer at the

specified offset and interprets the result as an unsigned integer. Supports
up to 48 bits of accuracy. For example:
const buf = Buffer.allocUnsafe(6);
buf.writeUInt16LE(0x90ab, 0);
buf.writeUInt32LE(0x12345678, 2);
buf.readUIntLE(0, 6).toString(16); // Specify 6 bytes (48 bits)
// Returns: '1234567890ab'
buf.readUIntBE(0, 6).toString(16);
// Returns: ab9078563412

Setting noAssert to true skips validation of the offset. This allows

the offset to be beyond the end of the Buffer.
buf.slice([start[, end]])#

start <Number> Default: 0

end <Number> Default: buffer.length

Return: <Buffer>

Returns a new Buffer that references the same memory as the original,
but offset and cropped by the start and end indices.
Note that modifying the new Buffer slice will modify the memory
in the original Buffer because the allocated memory of the two
objects overlap.
Example: build a Buffer with the ASCII alphabet, take a slice, then modify
one byte from the original Buffer.
const buf1 = Buffer.allocUnsafe(26);
for (var i = 0 ; i < 26 ; i++) {
buf1[i] = i + 97; // 97 is ASCII a
}
const buf2 = buf1.slice(0, 3);
buf2.toString('ascii', 0, buf2.length);
// Returns: 'abc'
buf1[0] = 33;
buf2.toString('ascii', 0, buf2.length);
// Returns : '!bc'
Specifying negative indexes causes the slice to be generated relative to
the end of the Buffer rather than the beginning.
const buf = Buffer.from('buffer');
buf.slice(-6, -1).toString();
// Returns 'buffe', equivalent to buf.slice(0, 5)

buf.slice(-6, -2).toString();
// Returns 'buff', equivalent to buf.slice(0, 4)
buf.slice(-5, -2).toString();
// Returns 'uff', equivalent to buf.slice(1, 4)
buf.swap16()#
Added in: v5.10.0

Return: <Buffer>

Interprets the Buffer as an array of unsigned 16-bit integers and swaps

the byte-order in-place. Throws a RangeError if the Bufferlength is not a
multiple of 16 bits. The method returns a reference to the Buffer, so calls
can be chained.
const buf = Buffer.from([0x1, 0x2, 0x3, 0x4, 0x5, 0x6, 0x7, 0x8]);
console.log(buf);
// Prints Buffer(0x1, 0x2, 0x3, 0x4, 0x5, 0x6, 0x7, 0x8)
buf.swap16();
console.log(buf);
// Prints Buffer(0x2, 0x1, 0x4, 0x3, 0x6, 0x5, 0x8, 0x7)
buf.swap32()#
Added in: v5.10.0

Return: <Buffer>

Interprets the Buffer as an array of unsigned 32-bit integers and swaps

the byte-order in-place. Throws a RangeError if the Bufferlength is not a
multiple of 32 bits. The method returns a reference to the Buffer, so calls
can be chained.
const buf = Buffer.from([0x1, 0x2, 0x3, 0x4, 0x5, 0x6, 0x7, 0x8]);
console.log(buf);
// Prints Buffer(0x1, 0x2, 0x3, 0x4, 0x5, 0x6, 0x7, 0x8)
buf.swap32();
console.log(buf);
// Prints Buffer(0x4, 0x3, 0x2, 0x1, 0x8, 0x7, 0x6, 0x5)
buf.toString([encoding[, start[, end]]])#

encoding <String> Default: 'utf8'

start <Number> Default: 0

end <Number> Default: buffer.length

Return: <String>

Decodes and returns a string from the Buffer data using the specified
character set encoding.
const buf = Buffer.allocUnsafe(26);
for (var i = 0 ; i < 26 ; i++) {
buf[i] = i + 97; // 97 is ASCII a
}
buf.toString('ascii');
// Returns: 'abcdefghijklmnopqrstuvwxyz'
buf.toString('ascii',0,5);
// Returns: 'abcde'
buf.toString('utf8',0,5);
// Returns: 'abcde'
buf.toString(undefined,0,5);
// Returns: 'abcde', encoding defaults to 'utf8'
buf.toJSON()#
Added in: v0.9.2

Return: <Object>

Returns a JSON representation of the Buffer

instance. JSON.stringify() implicitly calls this function when stringifying a
Buffer instance.
Example:
const buf = Buffer.from('test');
const json = JSON.stringify(buf);
console.log(json);
// Prints: '{"type":"Buffer","data":[116,101,115,116]}'
const copy = JSON.parse(json, (key, value) => {
return value && value.type === 'Buffer'
? Buffer.from(value.data)
: value;

});
console.log(copy.toString());
// Prints: 'test'
buf.values()#
Added in: v1.1.0

Return: <Iterator>

Creates and returns an iterator for Buffer values (bytes). This function is
called automatically when the Buffer is used in a for..ofstatement.
const buf = Buffer.from('buffer');
for (var value of buf.values()) {
console.log(value);
}
// prints:
// 98
// 117
// 102
// 102
// 101
// 114
for (var value of buf) {
console.log(value);
}
// prints:
// 98
// 117
// 102
// 102
// 101
// 114
buf.write(string[, offset[, length]][, encoding])#

string <String> Bytes to be written to buffer

offset <Number> Default: 0

length <Number> Default: buffer.length - offset

encoding <String> Default: 'utf8'

Return: <Number> Numbers of bytes written

Writes string to the Buffer at offset using the given encoding.

The length parameter is the number of bytes to write. If the Buffer did not
contain enough space to fit the entire string, only a partial amount of the
string will be written however, it will not write only partially encoded
characters.
const buf = Buffer.allocUnsafe(256);
const len = buf.write('\u00bd + \u00bc = \u00be', 0);
console.log(`${len} bytes: ${buf.toString('utf8', 0, len)}`);
// Prints: 12 bytes: + =
buf.writeDoubleBE(value, offset[, noAssert])#
buf.writeDoubleLE(value, offset[, noAssert])#

value <Number> Bytes to be written to Buffer

offset <Number> 0 <= offset <= buf.length - 8

noAssert <Boolean> Default: false

Return: <Number> The offset plus the number of written bytes

Writes value to the Buffer at the specified offset with specified endian
format (writeDoubleBE() writes big endian,writeDoubleLE() writes little
endian). The value argument should be a valid 64-bit double. Behavior is
not defined when value is anything other than a 64-bit double.
Set noAssert to true to skip validation of value and offset. This means
that value may be too large for the specific function andoffset may be
beyond the end of the Buffer leading to the values being silently dropped.
This should not be used unless you are certain of correctness.
Example:
const buf = Buffer.allocUnsafe(8);
buf.writeDoubleBE(0xdeadbeefcafebabe, 0);

console.log(buf);
// Prints: <Buffer 43 eb d5 b7 dd f9 5f d7>
buf.writeDoubleLE(0xdeadbeefcafebabe, 0);
console.log(buf);
// Prints: <Buffer d7 5f f9 dd b7 d5 eb 43>
buf.writeFloatBE(value, offset[, noAssert])#
buf.writeFloatLE(value, offset[, noAssert])#

value <Number> Bytes to be written to Buffer

offset <Number> 0 <= offset <= buf.length - 4

noAssert <Boolean> Default: false

Return: <Number> The offset plus the number of written bytes

Writes value to the Buffer at the specified offset with specified endian
format (writeFloatBE() writes big endian,writeFloatLE() writes little
endian). Behavior is not defined when value is anything other than a 32bit float.
Set noAssert to true to skip validation of value and offset. This means
that value may be too large for the specific function andoffset may be
beyond the end of the Buffer leading to the values being silently dropped.
This should not be used unless you are certain of correctness.
Example:
const buf = Buffer.allocUnsafe(4);
buf.writeFloatBE(0xcafebabe, 0);
console.log(buf);
// Prints: <Buffer 4f 4a fe bb>
buf.writeFloatLE(0xcafebabe, 0);
console.log(buf);
// Prints: <Buffer bb fe 4a 4f>

buf.writeInt8(value, offset[, noAssert])#

value <Number> Bytes to be written to Buffer

offset <Number> 0 <= offset <= buf.length - 1

noAssert <Boolean> Default: false

Return: <Number> The offset plus the number of written bytes

Writes value to the Buffer at the specified offset. The value should be a
valid signed 8-bit integer. Behavior is not defined whenvalue is anything
other than a signed 8-bit integer.
Set noAssert to true to skip validation of value and offset. This means
that value may be too large for the specific function andoffset may be
beyond the end of the Buffer leading to the values being silently dropped.
This should not be used unless you are certain of correctness.
The value is interpreted and written as a two's complement signed
integer.
const buf = Buffer.allocUnsafe(2);
buf.writeInt8(2, 0);
buf.writeInt8(-2, 1);
console.log(buf);
// Prints: <Buffer 02 fe>
buf.writeInt16BE(value, offset[, noAssert])#
buf.writeInt16LE(value, offset[, noAssert])#

value <Number> Bytes to be written to Buffer

offset <Number> 0 <= offset <= buf.length - 2

noAssert <Boolean> Default: false

Return: <Number> The offset plus the number of written bytes

Writes value to the Buffer at the specified offset with specified endian
format (writeInt16BE() writes big endian,writeInt16LE() writes little
endian). The value should be a valid signed 16-bit integer. Behavior is not
defined when value is anything other than a signed 16-bit integer.

Set noAssert to true to skip validation of value and offset. This means
that value may be too large for the specific function andoffset may be
beyond the end of the Buffer leading to the values being silently dropped.
This should not be used unless you are certain of correctness.
The value is interpreted and written as a two's complement signed
integer.
const buf = Buffer.allocUnsafe(4);
buf.writeInt16BE(0x0102,0);
buf.writeInt16LE(0x0304,2);
console.log(buf);
// Prints: <Buffer 01 02 04 03>
buf.writeInt32BE(value, offset[, noAssert])#
buf.writeInt32LE(value, offset[, noAssert])#

value <Number> Bytes to be written to Buffer

offset <Number> 0 <= offset <= buf.length - 4

noAssert <Boolean> Default: false

Return: <Number> The offset plus the number of written bytes

Writes value to the Buffer at the specified offset with specified endian
format (writeInt32BE() writes big endian,writeInt32LE() writes little
endian). The value should be a valid signed 32-bit integer. Behavior is not
defined when value is anything other than a signed 32-bit integer.
Set noAssert to true to skip validation of value and offset. This means
that value may be too large for the specific function andoffset may be
beyond the end of the Buffer leading to the values being silently dropped.
This should not be used unless you are certain of correctness.
The value is interpreted and written as a two's complement signed
integer.
const buf = Buffer.allocUnsafe(8);
buf.writeInt32BE(0x01020304,0);
buf.writeInt32LE(0x05060708,4);
console.log(buf);

// Prints: <Buffer 01 02 03 04 08 07 06 05>

buf.writeIntBE(value, offset, byteLength[, noAssert])#
buf.writeIntLE(value, offset, byteLength[, noAssert])#
Added in: v1.0.0

value <Number> Bytes to be written to Buffer

offset <Number> 0 <= offset <= buf.length - byteLength

byteLength <Number> 0 < byteLength <= 6

noAssert <Boolean> Default: false

Return: <Number> The offset plus the number of written bytes

Writes value to the Buffer at the specified offset and byteLength. Supports
up to 48 bits of accuracy. For example:
const buf1 = Buffer.allocUnsafe(6);
buf1.writeUIntBE(0x1234567890ab, 0, 6);
console.log(buf1);
// Prints: <Buffer 12 34 56 78 90 ab>
const buf2 = Buffer.allocUnsafe(6);
buf2.writeUIntLE(0x1234567890ab, 0, 6);
console.log(buf2);
// Prints: <Buffer ab 90 78 56 34 12>
Set noAssert to true to skip validation of value and offset. This means
that value may be too large for the specific function andoffset may be
beyond the end of the Buffer leading to the values being silently dropped.
This should not be used unless you are certain of correctness.
Behavior is not defined when value is anything other than an integer.
buf.writeUInt8(value, offset[, noAssert])#

value <Number> Bytes to be written to Buffer

offset <Number> 0 <= offset <= buf.length - 1

noAssert <Boolean> Default: false

Return: <Number> The offset plus the number of written bytes

Writes value to the Buffer at the specified offset. The value should be a
valid unsigned 8-bit integer. Behavior is not defined whenvalue is anything
other than an unsigned 8-bit integer.
Set noAssert to true to skip validation of value and offset. This means
that value may be too large for the specific function andoffset may be
beyond the end of the Buffer leading to the values being silently dropped.
This should not be used unless you are certain of correctness.
Example:
const buf = Buffer.allocUnsafe(4);
buf.writeUInt8(0x3, 0);
buf.writeUInt8(0x4, 1);
buf.writeUInt8(0x23, 2);
buf.writeUInt8(0x42, 3);
console.log(buf);
// Prints: <Buffer 03 04 23 42>
buf.writeUInt16BE(value, offset[, noAssert])#
buf.writeUInt16LE(value, offset[, noAssert])#

value <Number> Bytes to be written to Buffer

offset <Number> 0 <= offset <= buf.length - 2

noAssert <Boolean> Default: false

Return: <Number> The offset plus the number of written bytes

Writes value to the Buffer at the specified offset with specified endian
format (writeUInt16BE() writes big endian,writeUInt16LE() writes little
endian). The value should be a valid unsigned 16-bit integer. Behavior is
not defined when value is anything other than an unsigned 16-bit integer.
Set noAssert to true to skip validation of value and offset. This means
that value may be too large for the specific function andoffset may be
beyond the end of the Buffer leading to the values being silently dropped.
This should not be used unless you are certain of correctness.

Example:
const buf = Buffer.allocUnsafe(4);
buf.writeUInt16BE(0xdead, 0);
buf.writeUInt16BE(0xbeef, 2);
console.log(buf);
// Prints: <Buffer de ad be ef>
buf.writeUInt16LE(0xdead, 0);
buf.writeUInt16LE(0xbeef, 2);
console.log(buf);
// Prints: <Buffer ad de ef be>
buf.writeUInt32BE(value, offset[, noAssert])#
buf.writeUInt32LE(value, offset[, noAssert])#

value <Number> Bytes to be written to Buffer

offset <Number> 0 <= offset <= buf.length - 4

noAssert <Boolean> Default: false

Return: <Number> The offset plus the number of written bytes

Writes value to the Buffer at the specified offset with specified endian
format (writeUInt32BE() writes big endian,writeUInt32LE() writes little
endian). The value should be a valid unsigned 32-bit integer. Behavior is
not defined when value is anything other than an unsigned 32-bit integer.
Set noAssert to true to skip validation of value and offset. This means
that value may be too large for the specific function andoffset may be
beyond the end of the Buffer leading to the values being silently dropped.
This should not be used unless you are certain of correctness.
Example:
const buf = Buffer.allocUnsafe(4);
buf.writeUInt32BE(0xfeedface, 0);
console.log(buf);

// Prints: <Buffer fe ed fa ce>

buf.writeUInt32LE(0xfeedface, 0);
console.log(buf);
// Prints: <Buffer ce fa ed fe>
buf.writeUIntBE(value, offset, byteLength[, noAssert])#
buf.writeUIntLE(value, offset, byteLength[, noAssert])#

value <Number> Bytes to be written to Buffer

offset <Number> 0 <= offset <= buf.length - byteLength

byteLength <Number> 0 < byteLength <= 6

noAssert <Boolean> Default: false

Return: <Number> The offset plus the number of written bytes

Writes value to the Buffer at the specified offset and byteLength. Supports
up to 48 bits of accuracy. For example:
const buf = Buffer.allocUnsafe(6);
buf.writeUIntBE(0x1234567890ab, 0, 6);
console.log(buf);
// Prints: <Buffer 12 34 56 78 90 ab>
Set noAssert to true to skip validation of value and offset. This means
that value may be too large for the specific function andoffset may be
beyond the end of the Buffer leading to the values being silently dropped.
This should not be used unless you are certain of correctness.
Behavior is not defined when value is anything other than an unsigned
integer.
buffer.INSPECT_MAX_BYTES#

<Number> Default: 50

Returns the maximum number of bytes that will be returned

when buffer.inspect() is called. This can be overridden by user modules.
See util.inspect() for more details on buffer.inspect() behavior.

Note that this is a property on the buffer module as returned

by require('buffer'), not on the Buffer global or a Buffer instance.
Class: SlowBuffer#
Deprecated since: v6.0.0
Stability: 0 - Deprecated: Use
Buffer.allocUnsafeSlow(size) instead.
Returns an un-pooled Buffer.
In order to avoid the garbage collection overhead of creating many
individually allocated Buffers, by default allocations under 4KB are sliced
from a single larger allocated object. This approach improves both
performance and memory usage since v8 does not need to track and
cleanup as many Persistent objects.
In the case where a developer may need to retain a small chunk of
memory from a pool for an indeterminate amount of time, it may be
appropriate to create an un-pooled Buffer instance using SlowBuffer then
copy out the relevant bits.
// need to keep around a few small chunks of memory
const store = [];
socket.on('readable', () => {
var data = socket.read();
// allocate for retained data
var sb = SlowBuffer(10);
// copy the data into the new allocation
data.copy(sb, 0, 0, 10);
store.push(sb);
});
Use of SlowBuffer should be used only as a last resort after a developer
has observed undue memory retention in their applications.
new SlowBuffer(size)#
Deprecated since: v6.0.0

Stability: 0 - Deprecated: Use

Buffer.allocUnsafeSlow(size) instead.

size Number

Allocates a new SlowBuffer of size bytes. The size must be less than or
equal to the value of require('buffer').kMaxLength (on 64-bit
architectures, kMaxLength is (2^31)-1). Otherwise, a RangeError is
thrown. A zero-length Buffer will be created if a size less than or equal to 0
is specified.
The underlying memory for SlowBuffer instances is not initialized. The
contents of a newly created SlowBuffer are unknown and could contain
sensitive data. Use buf.fill(0) to initialize a SlowBuffer to zeroes.
const SlowBuffer = require('buffer').SlowBuffer;
const buf = new SlowBuffer(5);
console.log(buf);
// <Buffer 78 e0 82 02 01>
// (octets will be different, every time)
buf.fill(0);
console.log(buf);
// <Buffer 00 00 00 00 00>

Addons

Hello world

Building

Linking to Node.js' own dependencies

Loading Addons using require()

Native Abstractions for Node.js

Addon examples

Function arguments

Callbacks

Object factory

Function factory

Wrapping C++ objects

Factory of wrapped objects

Passing wrapped objects around

AtExit hooks

void AtExit(callback, args)

Addons#
Node.js Addons are dynamically-linked shared objects, written in C or C+
+, that can be loaded into Node.js using the require()function, and used
just as if they were an ordinary Node.js module. They are used primarily to
provide an interface between JavaScript running in Node.js and C/C++
libraries.
At the moment, the method for implementing Addons is rather
complicated, involving knowledge of several components and APIs :

V8: the C++ library Node.js currently uses to provide the JavaScript
implementation. V8 provides the mechanisms for creating objects,
calling functions, etc. V8's API is documented mostly in
the v8.h header file (deps/v8/include/v8.h in the Node.js source tree),
which is also available online.

libuv: The C library that implements the Node.js event loop, its
worker threads and all of the asynchronous behaviors of the platform.
It also serves as a cross-platform abstraction library, giving easy,
POSIX-like access across all major operating systems to many
common system tasks, such as interacting with the filesystem,
sockets, timers and system events. libuv also provides a pthreads-like
threading abstraction that may be used to power more sophisticated
asynchronous Addons that need to move beyond the standard event
loop. Addon authors are encouraged to think about how to avoid
blocking the event loop with I/O or other time-intensive tasks by offloading work via libuv to non-blocking system operations, worker
threads or a custom use of libuv's threads.

Internal Node.js libraries. Node.js itself exports a number of C/C++

APIs that Addons can use the most important of which is
thenode::ObjectWrap class.

Node.js includes a number of other statically linked libraries

including OpenSSL. These other libraries are located in
the deps/directory in the Node.js source tree. Only the V8 and
OpenSSL symbols are purposefully re-exported by Node.js and may be
used to various extents by Addons. See Linking to Node.js' own
dependencies for additional information.

All of the following examples are available for download and may be used
as a starting-point for your own Addon.
Hello world#
This "Hello world" example is a simple Addon, written in C++, that is the
equivalent of the following JavaScript code:
module.exports.hello = () => 'world';
First, create the file hello.cc:
// hello.cc
#include <node.h>
namespace demo {
using
using
using
using
using
using

v8::FunctionCallbackInfo;
v8::Isolate;
v8::Local;
v8::Object;
v8::String;
v8::Value;

void Method(const FunctionCallbackInfo<Value>& args) {

Isolate* isolate = args.GetIsolate();
args.GetReturnValue().Set(String::NewFromUtf8(isolate, "world"));
}

void init(Local<Object> exports) {

NODE_SET_METHOD(exports, "hello", Method);
}
NODE_MODULE(addon, init)
} // namespace demo
Note that all Node.js Addons must export an initialization function
following the pattern:
void Initialize(Local<Object> exports);
NODE_MODULE(module_name, Initialize)
There is no semi-colon after NODE_MODULE as it's not a function
(see node.h).
The module_name must match the filename of the final binary (excluding
the .node suffix).
In the hello.cc example, then, the initialization function is init and the
Addon module name is addon.
Building#
Once the source code has been written, it must be compiled into the
binary addon.node file. To do so, create a file called binding.gypin the toplevel of the project describing the build configuration of your module using
a JSON-like format. This file is used by node-gyp -- a tool written
specifically to compile Node.js Addons.
{
"targets": [
{
"target_name": "addon",
"sources": [ "hello.cc" ]
}
]
}

Note: A version of the node-gyp utility is bundled and distributed with

Node.js as part of npm. This version is not made directly available for
developers to use and is intended only to support the ability to use
the npm install command to compile and install Addons. Developers who
wish to use node-gyp directly can install it using the command npm install
-g node-gyp. See the node-gyp installation instructions for more
information, including platform-specific requirements.
Once the binding.gyp file has been created, use node-gyp configure to
generate the appropriate project build files for the current platform. This
will generate either a Makefile (on Unix platforms) or a vcxproj file (on
Windows) in the build/ directory.
Next, invoke the node-gyp build command to generate the
compiled addon.node file. This will be put into the build/Release/directory.
When using npm install to install a Node.js Addon, npm uses its own
bundled version of node-gyp to perform this same set of actions,
generating a compiled version of the Addon for the user's platform on
demand.
Once built, the binary Addon can be used from within Node.js by
pointing require() to the built addon.node module:
// hello.js
const addon = require('./build/Release/addon');
console.log(addon.hello()); // 'world'
Please see the examples below for further information
or https://github.com/arturadib/node-qt for an example in production.
Because the exact path to the compiled Addon binary can vary depending
on how it is compiled (i.e. sometimes it may be in./build/Debug/), Addons
can use the bindings package to load the compiled module.
Note that while the bindings package implementation is more
sophisticated in how it locates Addon modules, it is essentially using a trycatch pattern similar to:

try {
return require('./build/Release/addon.node');
} catch (err) {
return require('./build/Debug/addon.node');
}
Linking to Node.js' own dependencies#
Node.js uses a number of statically linked libraries such as V8, libuv and
OpenSSL. All Addons are required to link to V8 and may link to any of the
other dependencies as well. Typically, this is as simple as including the
appropriate #include <...> statements (e.g.#include <v8.h>) and nodegyp will locate the appropriate headers automatically. However, there are
a few caveats to be aware of:

When node-gyp runs, it will detect the specific release version of

Node.js and download either the full source tarball or just the headers.
If the full source is downloaded, Addons will have complete access to
the full set of Node.js dependencies. However, if only the Node.js
headers are downloaded, then only the symbols exported by Node.js
will be available.

node-gyp can be run using the --nodedir flag pointing at a local

Node.js source image. Using this option, the Addon will have access to
the full set of dependencies.

Loading Addons using require()#

The filename extension of the compiled Addon binary is .node (as opposed
to .dll or .so). The require() function is written to look for files with
the .node file extension and initialize those as dynamically-linked libraries.
When calling require(), the .node extension can usually be omitted and
Node.js will still find and initialize the Addon. One caveat, however, is that
Node.js will first attempt to locate and load modules or JavaScript files
that happen to share the same base name. For instance, if there is a
file addon.js in the same directory as the binary addon.node,
then require('addon') will give precedence to theaddon.js file and load it
instead.
Native Abstractions for Node.js#

Each of the examples illustrated in this document make direct use of the
Node.js and V8 APIs for implementing Addons. It is important to
understand that the V8 API can, and has, changed dramatically from one
V8 release to the next (and one major Node.js release to the next). With
each change, Addons may need to be updated and recompiled in order to
continue functioning. The Node.js release schedule is designed to
minimize the frequency and impact of such changes but there is little that
Node.js can do currently to ensure stability of the V8 APIs.
The Native Abstractions for Node.js (or nan) provide a set of tools that
Addon developers are recommended to use to keep compatibility between
past and future releases of V8 and Node.js. See the nan examples for an
illustration of how it can be used.
Addon examples#
Following are some example Addons intended to help developers get
started. The examples make use of the V8 APIs. Refer to the online V8
reference for help with the various V8 calls, and V8's Embedder's
Guide for an explanation of several concepts used such as handles,
scopes, function templates, etc.
Each of these examples using the following binding.gyp file:
{
"targets": [
{
"target_name": "addon",
"sources": [ "addon.cc" ]
}
]
}
In cases where there is more than one .cc file, simply add the additional
filename to the sources array. For example:
"sources": ["addon.cc", "myexample.cc"]
Once the binding.gyp file is ready, the example Addons can be configured
and built using node-gyp:

$ node-gyp configure build

Function arguments#
Addons will typically expose objects and functions that can be accessed
from JavaScript running within Node.js. When functions are invoked from
JavaScript, the input arguments and return value must be mapped to and
from the C/C++ code.
The following example illustrates how to read function arguments passed
from JavaScript and how to return a result:
// addon.cc
#include <node.h>
namespace demo {
using
using
using
using
using
using
using
using

v8::Exception;
v8::FunctionCallbackInfo;
v8::Isolate;
v8::Local;
v8::Number;
v8::Object;
v8::String;
v8::Value;

// This is the implementation of the "add" method

// Input arguments are passed using the
// const FunctionCallbackInfo<Value>& args struct
void Add(const FunctionCallbackInfo<Value>& args) {
Isolate* isolate = args.GetIsolate();
// Check the number of arguments passed.
if (args.Length() < 2) {
// Throw an Error that is passed back to JavaScript
isolate->ThrowException(Exception::TypeError(
String::NewFromUtf8(isolate, "Wrong number of arguments")));
return;
}

// Check the argument types

if (!args[0]->IsNumber() || !args[1]->IsNumber()) {
isolate->ThrowException(Exception::TypeError(
String::NewFromUtf8(isolate, "Wrong arguments")));
return;
}
// Perform the operation
double value = args[0]->NumberValue() + args[1]->NumberValue();
Local<Number> num = Number::New(isolate, value);
// Set the return value (using the passed in
// FunctionCallbackInfo<Value>&)
args.GetReturnValue().Set(num);
}
void Init(Local<Object> exports) {
NODE_SET_METHOD(exports, "add", Add);
}
NODE_MODULE(addon, Init)
} // namespace demo
Once compiled, the example Addon can be required and used from within
Node.js:
// test.js
const addon = require('./build/Release/addon');
console.log('This should be eight:', addon.add(3, 5));
Callbacks#
It is common practice within Addons to pass JavaScript functions to a C++
function and execute them from there. The following example illustrates
how to invoke such callbacks:
// addon.cc
#include <node.h>

namespace demo {
using
using
using
using
using
using
using
using

v8::Function;
v8::FunctionCallbackInfo;
v8::Isolate;
v8::Local;
v8::Null;
v8::Object;
v8::String;
v8::Value;

void RunCallback(const FunctionCallbackInfo<Value>& args) {

Isolate* isolate = args.GetIsolate();
Local<Function> cb = Local<Function>::Cast(args[0]);
const unsigned argc = 1;
Local<Value> argv[argc] = { String::NewFromUtf8(isolate, "hello
world") };
cb->Call(Null(isolate), argc, argv);
}
void Init(Local<Object> exports, Local<Object> module) {
NODE_SET_METHOD(module, "exports", RunCallback);
}
NODE_MODULE(addon, Init)
} // namespace demo
Note that this example uses a two-argument form of Init() that receives
the full module object as the second argument. This allows the Addon to
completely overwrite exports with a single function instead of adding the
function as a property of exports.
To test it, run the following JavaScript:
// test.js
const addon = require('./build/Release/addon');

addon((msg) => {
console.log(msg); // 'hello world'
});
Note that, in this example, the callback function is invoked synchronously.
Object factory#
Addons can create and return new objects from within a C++ function as
illustrated in the following example. An object is created and returned with
a property msg that echoes the string passed to createObject():
// addon.cc
#include <node.h>
namespace demo {
using
using
using
using
using
using

v8::FunctionCallbackInfo;
v8::Isolate;
v8::Local;
v8::Object;
v8::String;
v8::Value;

void CreateObject(const FunctionCallbackInfo<Value>& args) {

Isolate* isolate = args.GetIsolate();
Local<Object> obj = Object::New(isolate);
obj->Set(String::NewFromUtf8(isolate, "msg"), args[0]->ToString());
args.GetReturnValue().Set(obj);
}
void Init(Local<Object> exports, Local<Object> module) {
NODE_SET_METHOD(module, "exports", CreateObject);
}
NODE_MODULE(addon, Init)

} // namespace demo
To test it in JavaScript:
// test.js
const addon = require('./build/Release/addon');
var obj1 = addon('hello');
var obj2 = addon('world');
console.log(obj1.msg + ' ' + obj2.msg); // 'hello world'
Function factory#
Another common scenario is creating JavaScript functions that wrap C++
functions and returning those back to JavaScript:
// addon.cc
#include <node.h>
namespace demo {
using
using
using
using
using
using
using
using

v8::Function;
v8::FunctionCallbackInfo;
v8::FunctionTemplate;
v8::Isolate;
v8::Local;
v8::Object;
v8::String;
v8::Value;

void MyFunction(const FunctionCallbackInfo<Value>& args) {

Isolate* isolate = args.GetIsolate();
args.GetReturnValue().Set(String::NewFromUtf8(isolate, "hello
world"));
}
void CreateFunction(const FunctionCallbackInfo<Value>& args) {
Isolate* isolate = args.GetIsolate();

Local<FunctionTemplate> tpl = FunctionTemplate::New(isolate,

MyFunction);
Local<Function> fn = tpl->GetFunction();
// omit this to make it anonymous
fn->SetName(String::NewFromUtf8(isolate, "theFunction"));
args.GetReturnValue().Set(fn);
}
void Init(Local<Object> exports, Local<Object> module) {
NODE_SET_METHOD(module, "exports", CreateFunction);
}
NODE_MODULE(addon, Init)
} // namespace demo
To test:
// test.js
const addon = require('./build/Release/addon');
var fn = addon();
console.log(fn()); // 'hello world'
Wrapping C++ objects#
It is also possible to wrap C++ objects/classes in a way that allows new
instances to be created using the JavaScript new operator:
// addon.cc
#include <node.h>
#include "myobject.h"
namespace demo {
using v8::Local;
using v8::Object;

void InitAll(Local<Object> exports) {

MyObject::Init(exports);
}
NODE_MODULE(addon, InitAll)
} // namespace demo
Then, in myobject.h, the wrapper class inherits from node::ObjectWrap:
// myobject.h
#ifndef MYOBJECT_H
#define MYOBJECT_H
#include <node.h>
#include <node_object_wrap.h>
namespace demo {
class MyObject : public node::ObjectWrap {
public:
static void Init(v8::Local<v8::Object> exports);
private:
explicit MyObject(double value = 0);
~MyObject();
static void New(const v8::FunctionCallbackInfo<v8::Value>& args);
static void PlusOne(const v8::FunctionCallbackInfo<v8::Value>&
args);
static v8::Persistent<v8::Function> constructor;
double value_;
};
} // namespace demo
#endif

In myobject.cc, implement the various methods that are to be exposed.

Below, the method plusOne() is exposed by adding it to the constructor's
prototype:
// myobject.cc
#include "myobject.h"
namespace demo {
using
using
using
using
using
using
using
using
using
using
using

v8::Context;
v8::Function;
v8::FunctionCallbackInfo;
v8::FunctionTemplate;
v8::Isolate;
v8::Local;
v8::Number;
v8::Object;
v8::Persistent;
v8::String;
v8::Value;

Persistent<Function> MyObject::constructor;
MyObject::MyObject(double value) : value_(value) {
}
MyObject::~MyObject() {
}
void MyObject::Init(Local<Object> exports) {
Isolate* isolate = exports->GetIsolate();
// Prepare constructor template
Local<FunctionTemplate> tpl = FunctionTemplate::New(isolate,
New);
tpl->SetClassName(String::NewFromUtf8(isolate, "MyObject"));
tpl->InstanceTemplate()->SetInternalFieldCount(1);

// Prototype
NODE_SET_PROTOTYPE_METHOD(tpl, "plusOne", PlusOne);
constructor.Reset(isolate, tpl->GetFunction());
exports->Set(String::NewFromUtf8(isolate, "MyObject"),
tpl->GetFunction());
}
void MyObject::New(const FunctionCallbackInfo<Value>& args) {
Isolate* isolate = args.GetIsolate();
if (args.IsConstructCall()) {
// Invoked as constructor: `new MyObject(...)`
double value = args[0]->IsUndefined() ? 0 : args[0]>NumberValue();
MyObject* obj = new MyObject(value);
obj->Wrap(args.This());
args.GetReturnValue().Set(args.This());
} else {
// Invoked as plain function `MyObject(...)`, turn into construct call.
const int argc = 1;
Local<Value> argv[argc] = { args[0] };
Local<Context> context = isolate->GetCurrentContext();
Local<Function> cons = Local<Function>::New(isolate,
constructor);
Local<Object> result =
cons->NewInstance(context, argc, argv).ToLocalChecked();
args.GetReturnValue().Set(result);
}
}
void MyObject::PlusOne(const FunctionCallbackInfo<Value>& args) {
Isolate* isolate = args.GetIsolate();
MyObject* obj = ObjectWrap::Unwrap<MyObject>(args.Holder());
obj->value_ += 1;
args.GetReturnValue().Set(Number::New(isolate, obj->value_));

}
} // namespace demo
To build this example, the myobject.cc file must be added to
the binding.gyp:
{
"targets": [
{
"target_name": "addon",
"sources": [
"addon.cc",
"myobject.cc"
]
}
]
}
Test it with:
// test.js
const addon = require('./build/Release/addon');
var obj = new addon.MyObject(10);
console.log(obj.plusOne()); // 11
console.log(obj.plusOne()); // 12
console.log(obj.plusOne()); // 13
Factory of wrapped objects#
Alternatively, it is possible to use a factory pattern to avoid explicitly
creating object instances using the JavaScript new operator:
var obj = addon.createObject();
// instead of:
// var obj = new addon.Object();
First, the createObject() method is implemented in addon.cc:
// addon.cc

#include <node.h>
#include "myobject.h"
namespace demo {
using
using
using
using
using
using

v8::FunctionCallbackInfo;
v8::Isolate;
v8::Local;
v8::Object;
v8::String;
v8::Value;

void CreateObject(const FunctionCallbackInfo<Value>& args) {

MyObject::NewInstance(args);
}
void InitAll(Local<Object> exports, Local<Object> module) {
MyObject::Init(exports->GetIsolate());
NODE_SET_METHOD(module, "exports", CreateObject);
}
NODE_MODULE(addon, InitAll)
} // namespace demo
In myobject.h, the static method NewInstance() is added to handle
instantiating the object. This method takes the place of using newin
JavaScript:
// myobject.h
#ifndef MYOBJECT_H
#define MYOBJECT_H
#include <node.h>
#include <node_object_wrap.h>
namespace demo {

class MyObject : public node::ObjectWrap {

public:
static void Init(v8::Isolate* isolate);
static void NewInstance(const v8::FunctionCallbackInfo<v8::Value>&
args);
private:
explicit MyObject(double value = 0);
~MyObject();
static void New(const v8::FunctionCallbackInfo<v8::Value>& args);
static void PlusOne(const v8::FunctionCallbackInfo<v8::Value>&
args);
static v8::Persistent<v8::Function> constructor;
double value_;
};
} // namespace demo
#endif
The implementation in myobject.cc is similar to the previous example:
// myobject.cc
#include <node.h>
#include "myobject.h"
namespace demo {
using
using
using
using
using
using
using
using
using
using

v8::Context;
v8::Function;
v8::FunctionCallbackInfo;
v8::FunctionTemplate;
v8::Isolate;
v8::Local;
v8::Number;
v8::Object;
v8::Persistent;
v8::String;

using v8::Value;
Persistent<Function> MyObject::constructor;
MyObject::MyObject(double value) : value_(value) {
}
MyObject::~MyObject() {
}
void MyObject::Init(Isolate* isolate) {
// Prepare constructor template
Local<FunctionTemplate> tpl = FunctionTemplate::New(isolate,
New);
tpl->SetClassName(String::NewFromUtf8(isolate, "MyObject"));
tpl->InstanceTemplate()->SetInternalFieldCount(1);
// Prototype
NODE_SET_PROTOTYPE_METHOD(tpl, "plusOne", PlusOne);
constructor.Reset(isolate, tpl->GetFunction());
}
void MyObject::New(const FunctionCallbackInfo<Value>& args) {
Isolate* isolate = args.GetIsolate();
if (args.IsConstructCall()) {
// Invoked as constructor: `new MyObject(...)`
double value = args[0]->IsUndefined() ? 0 : args[0]>NumberValue();
MyObject* obj = new MyObject(value);
obj->Wrap(args.This());
args.GetReturnValue().Set(args.This());
} else {
// Invoked as plain function `MyObject(...)`, turn into construct call.
const int argc = 1;
Local<Value> argv[argc] = { args[0] };

Local<Function> cons = Local<Function>::New(isolate,

constructor);
Local<Context> context = isolate->GetCurrentContext();
Local<Object> instance =
cons->NewInstance(context, argc, argv).ToLocalChecked();
args.GetReturnValue().Set(instance);
}
}
void MyObject::NewInstance(const FunctionCallbackInfo<Value>&
args) {
Isolate* isolate = args.GetIsolate();
const unsigned argc = 1;
Local<Value> argv[argc] = { args[0] };
Local<Function> cons = Local<Function>::New(isolate, constructor);
Local<Context> context = isolate->GetCurrentContext();
Local<Object> instance =
cons->NewInstance(context, argc, argv).ToLocalChecked();
args.GetReturnValue().Set(instance);
}
void MyObject::PlusOne(const FunctionCallbackInfo<Value>& args) {
Isolate* isolate = args.GetIsolate();
MyObject* obj = ObjectWrap::Unwrap<MyObject>(args.Holder());
obj->value_ += 1;
args.GetReturnValue().Set(Number::New(isolate, obj->value_));
}
} // namespace demo
Once again, to build this example, the myobject.cc file must be added to
the binding.gyp:
{
"targets": [

{
"target_name": "addon",
"sources": [
"addon.cc",
"myobject.cc"
]
}
]
}
Test it with:
// test.js
const createObject = require('./build/Release/addon');
var obj = createObject(10);
console.log(obj.plusOne()); // 11
console.log(obj.plusOne()); // 12
console.log(obj.plusOne()); // 13
var obj2 = createObject(20);
console.log(obj2.plusOne()); // 21
console.log(obj2.plusOne()); // 22
console.log(obj2.plusOne()); // 23
Passing wrapped objects around#
In addition to wrapping and returning C++ objects, it is possible to pass
wrapped objects around by unwrapping them with the Node.js helper
function node::ObjectWrap::Unwrap. The following examples shows a
function add() that can take two MyObject objects as input arguments:
// addon.cc
#include <node.h>
#include <node_object_wrap.h>
#include "myobject.h"
namespace demo {
using v8::FunctionCallbackInfo;

using
using
using
using
using
using

v8::Isolate;
v8::Local;
v8::Number;
v8::Object;
v8::String;
v8::Value;

void CreateObject(const FunctionCallbackInfo<Value>& args) {

MyObject::NewInstance(args);
}
void Add(const FunctionCallbackInfo<Value>& args) {
Isolate* isolate = args.GetIsolate();
MyObject* obj1 = node::ObjectWrap::Unwrap<MyObject>(
args[0]->ToObject());
MyObject* obj2 = node::ObjectWrap::Unwrap<MyObject>(
args[1]->ToObject());
double sum = obj1->value() + obj2->value();
args.GetReturnValue().Set(Number::New(isolate, sum));
}
void InitAll(Local<Object> exports) {
MyObject::Init(exports->GetIsolate());
NODE_SET_METHOD(exports, "createObject", CreateObject);
NODE_SET_METHOD(exports, "add", Add);
}
NODE_MODULE(addon, InitAll)
} // namespace demo
In myobject.h, a new public method is added to allow access to private
values after unwrapping the object.
// myobject.h
#ifndef MYOBJECT_H

#define MYOBJECT_H
#include <node.h>
#include <node_object_wrap.h>
namespace demo {
class MyObject : public node::ObjectWrap {
public:
static void Init(v8::Isolate* isolate);
static void NewInstance(const v8::FunctionCallbackInfo<v8::Value>&
args);
inline double value() const { return value_; }
private:
explicit MyObject(double value = 0);
~MyObject();
static void New(const v8::FunctionCallbackInfo<v8::Value>& args);
static v8::Persistent<v8::Function> constructor;
double value_;
};
} // namespace demo
#endif
The implementation of myobject.cc is similar to before:
// myobject.cc
#include <node.h>
#include "myobject.h"
namespace demo {
using
using
using
using

v8::Context;
v8::Function;
v8::FunctionCallbackInfo;
v8::FunctionTemplate;

using
using
using
using
using
using

v8::Isolate;
v8::Local;
v8::Object;
v8::Persistent;
v8::String;
v8::Value;

Persistent<Function> MyObject::constructor;
MyObject::MyObject(double value) : value_(value) {
}
MyObject::~MyObject() {
}
void MyObject::Init(Isolate* isolate) {
// Prepare constructor template
Local<FunctionTemplate> tpl = FunctionTemplate::New(isolate,
New);
tpl->SetClassName(String::NewFromUtf8(isolate, "MyObject"));
tpl->InstanceTemplate()->SetInternalFieldCount(1);
constructor.Reset(isolate, tpl->GetFunction());
}
void MyObject::New(const FunctionCallbackInfo<Value>& args) {
Isolate* isolate = args.GetIsolate();
if (args.IsConstructCall()) {
// Invoked as constructor: `new MyObject(...)`
double value = args[0]->IsUndefined() ? 0 : args[0]>NumberValue();
MyObject* obj = new MyObject(value);
obj->Wrap(args.This());
args.GetReturnValue().Set(args.This());
} else {
// Invoked as plain function `MyObject(...)`, turn into construct call.
const int argc = 1;

Local<Value> argv[argc] = { args[0] };

Local<Context> context = isolate->GetCurrentContext();
Local<Function> cons = Local<Function>::New(isolate,
constructor);
Local<Object> instance =
cons->NewInstance(context, argc, argv).ToLocalChecked();
args.GetReturnValue().Set(instance);
}
}
void MyObject::NewInstance(const FunctionCallbackInfo<Value>&
args) {
Isolate* isolate = args.GetIsolate();
const unsigned argc = 1;
Local<Value> argv[argc] = { args[0] };
Local<Function> cons = Local<Function>::New(isolate, constructor);
Local<Context> context = isolate->GetCurrentContext();
Local<Object> instance =
cons->NewInstance(context, argc, argv).ToLocalChecked();
args.GetReturnValue().Set(instance);
}
} // namespace demo
Test it with:
// test.js
const addon = require('./build/Release/addon');
var obj1 = addon.createObject(10);
var obj2 = addon.createObject(20);
var result = addon.add(obj1, obj2);
console.log(result); // 30

AtExit hooks#
An "AtExit" hook is a function that is invoked after the Node.js event loop
has ended by before the JavaScript VM is terminated and Node.js shuts
down. "AtExit" hooks are registered using the node::AtExit API.
void AtExit(callback, args)#

callback: void (*)(void*) - A pointer to the function to call at exit.

args: void* - A pointer to pass to the callback at exit.

Registers exit hooks that run after the event loop has ended but before
the VM is killed.
AtExit takes two parameters: a pointer to a callback function to run at exit,
and a pointer to untyped context data to be passed to that callback.
Callbacks are run in last-in first-out order.
The following addon.cc implements AtExit:
// addon.cc
#undef NDEBUG
#include <assert.h>
#include <stdlib.h>
#include <node.h>
namespace demo {
using
using
using
using
using

node::AtExit;
v8::HandleScope;
v8::Isolate;
v8::Local;
v8::Object;

static char cookie[] = "yum yum";

static int at_exit_cb1_called = 0;
static int at_exit_cb2_called = 0;
static void at_exit_cb1(void* arg) {

Isolate* isolate = static_cast<Isolate*>(arg);

HandleScope scope(isolate);
Local<Object> obj = Object::New(isolate);
assert(!obj.IsEmpty()); // assert VM is still alive
assert(obj->IsObject());
at_exit_cb1_called++;
}
static void at_exit_cb2(void* arg) {
assert(arg == static_cast<void*>(cookie));
at_exit_cb2_called++;
}
static void sanity_check(void*) {
assert(at_exit_cb1_called == 1);
assert(at_exit_cb2_called == 2);
}
void init(Local<Object> exports) {
AtExit(sanity_check);
AtExit(at_exit_cb2, cookie);
AtExit(at_exit_cb2, cookie);
AtExit(at_exit_cb1, exports->GetIsolate());
}
NODE_MODULE(addon, init);
} // namespace demo
Test in JavaScript by running:
// test.js
const addon = require('./build/Release/addon');
Child Process

Asynchronous Process Creation

Spawning .bat and .cmd files on Windows

child_process.exec(command[, options][, callback])

child_process.execFile(file[, args][, options][, callback])

child_process.fork(modulePath[, args][, options])

child_process.spawn(command[, args][, options])

options.detached

options.stdio

Synchronous Process Creation

child_process.execFileSync(file[, args][, options])

child_process.execSync(command[, options])

child_process.spawnSync(command[, args][, options])

Class: ChildProcess

Event: 'close'

Event: 'disconnect'

Event: 'error'

Event: 'exit'

Event: 'message'

child.connected

child.disconnect()

child.kill([signal])

child.pid

child.send(message[, sendHandle[, options]][, callback])

Example: sending a server object

Example: sending a socket object

child.stderr

child.stdin

child.stdio

child.stdout

maxBuffer and Unicode

Child Process#
Stability: 2 - Stable
The child_process module provides the ability to spawn child processes in
a manner that is similar, but not identical, to popen(3). This capability is
primarily provided by the child_process.spawn() function:
const spawn = require('child_process').spawn;
const ls = spawn('ls', ['-lh', '/usr']);
ls.stdout.on('data', (data) => {
console.log(`stdout: ${data}`);
});
ls.stderr.on('data', (data) => {
console.log(`stderr: ${data}`);
});
ls.on('close', (code) => {
console.log(`child process exited with code ${code}`);
});
By default, pipes for stdin, stdout and stderr are established between the
parent Node.js process and the spawned child. It is possible to stream
data through these pipes in a non-blocking way. Note, however, that some
programs use line-buffered I/O internally. While that does not affect
Node.js, it can mean that data sent to the child process may not be
immediately consumed.
The child_process.spawn() method spawns the child process
asynchronously, without blocking the Node.js event loop.
Thechild_process.spawnSync() function provides equivalent functionality

in a synchronous manner that blocks the event loop until the spawned
process either exits or is terminated.
For convenience, the child_process module provides a handful of
synchronous and asynchronous alternatives
tochild_process.spawn() and child_process.spawnSync(). Note that each of
these alternatives are implemented on top
ofchild_process.spawn() or child_process.spawnSync().

child_process.exec(): spawns a shell and runs a command within

that shell, passing the stdout and stderr to a callback function when
complete.

child_process.execFile(): similar to child_process.exec() except that

it spawns the command directly without first spawning a shell.

child_process.fork(): spawns a new Node.js process and invokes a

specified module with an IPC communication channel established that
allows sending messages between parent and child.

child_process.execSync(): a synchronous version

of child_process.exec() that will block the Node.js event loop.

child_process.execFileSync(): a synchronous version

of child_process.execFile() that will block the Node.js event loop.

For certain use cases, such as automating shell scripts, the synchronous
counterparts may be more convenient. In many cases, however, the
synchronous methods can have significant impact on performance due to
stalling the event loop while spawned processes complete.
Asynchronous Process Creation#
The child_process.spawn(), child_process.fork(), child_process.exec(),
and child_process.execFile() methods all follow the idiomatic
asynchronous programming pattern typical of other Node.js APIs.
Each of the methods returns a ChildProcess instance. These objects
implement the Node.js EventEmitter API, allowing the parent process to
register listener functions that are called when certain events occur during
the life cycle of the child process.

The child_process.exec() and child_process.execFile() methods additionally

allow for an optional callback function to be specified that is invoked when
the child process terminates.
Spawning .bat and .cmd files on Windows#
The importance of the distinction
between child_process.exec() and child_process.execFile() can vary based
on platform. On Unix-type operating systems (Unix, Linux,
OSX) child_process.execFile() can be more efficient because it does not
spawn a shell. On Windows, however, .bat and .cmd files are not
executable on their own without a terminal, and therefore cannot be
launched usingchild_process.execFile(). When running on
Windows, .bat and .cmd files can be invoked
using child_process.spawn() with theshell option set,
with child_process.exec(), or by spawning cmd.exe and passing
the .bat or .cmd file as an argument (which is what the shell option
and child_process.exec() do).
// On Windows Only ...
const spawn = require('child_process').spawn;
const bat = spawn('cmd.exe', ['/c', 'my.bat']);
bat.stdout.on('data', (data) => {
console.log(data);
});
bat.stderr.on('data', (data) => {
console.log(data);
});
bat.on('exit', (code) => {
console.log(`Child exited with code ${code}`);
});
// OR...
const exec = require('child_process').exec;
exec('my.bat', (err, stdout, stderr) => {
if (err) {

console.error(err);
return;
}
console.log(stdout);
});
child_process.exec(command[, options][, callback])#

command <String> The command to run, with space-separated

arguments
options <Object>
o

cwd <String> Current working directory of the child process

env <Object> Environment key-value pairs

encoding <String> (Default: 'utf8')

o
o

shell <String> Shell to execute the command with

(Default: '/bin/sh' on UNIX, 'cmd.exe' on Windows, The shell should
understand the -c switch on UNIX or /s /c on Windows. On
Windows, command line parsing should be compatible
withcmd.exe.)
timeout <Number> (Default: 0)
maxBuffer <Number> largest amount of data (in bytes)
allowed on stdout or stderr - if exceeded child process is killed
(Default:200\*1024)
killSignal <String> (Default: 'SIGTERM')

uid <Number> Sets the user identity of the process.

(See setuid(2).)

gid <Number> Sets the group identity of the process.

(See setgid(2).)

callback <Function> called with the output when process terminates

o

error <Error>

stdout <String> | <Buffer>

stderr <String> | <Buffer>

Return: <ChildProcess>

Spawns a shell then executes the command within that shell, buffering
any generated output.
const exec = require('child_process').exec;
exec('cat *.js bad_file | wc -l', (error, stdout, stderr) => {
if (error) {
console.error(`exec error: ${error}`);
return;
}
console.log(`stdout: ${stdout}`);
console.log(`stderr: ${stderr}`);
});
If a callback function is provided, it is called with the arguments (error,
stdout, stderr). On success, error will be null. On error, error will be an
instance of Error. The error.code property will be the exit code of the child
process while error.signal will be set to the signal that terminated the
process. Any exit code other than 0 is considered to be an error.
The stdout and stderr arguments passed to the callback will contain the
stdout and stderr output of the child process. By default, Node.js will
decode the output as UTF-8 and pass strings to the callback.
The encoding option can be used to specify the character encoding used
to decode the stdout and stderr output.
If encoding is 'buffer', Buffer objects will be passed to the callback instead.
The options argument may be passed as the second argument to
customize how the process is spawned. The default options are:
{
encoding: 'utf8',
timeout: 0,
maxBuffer: 200*1024,
killSignal: 'SIGTERM',
cwd: null,
env: null
}

If timeout is greater than 0, the parent will send the the signal identified
by the killSignal property (the default is 'SIGTERM') if the child runs longer
than timeout milliseconds.
Note: Unlike the exec(3) POSIX system call, child_process.exec() does not
replace the existing process and uses a shell to execute the command.
child_process.execFile(file[, args][, options][, callback])#

file <String> The name or path of the executable file to run

args <Array> List of string arguments

options <Object>
o

cwd <String> Current working directory of the child process

env <Object> Environment key-value pairs

encoding <String> (Default: 'utf8')

timeout <Number> (Default: 0)

maxBuffer <Number> largest amount of data (in bytes)

allowed on stdout or stderr - if exceeded child process is killed
(Default:200\*1024)
killSignal <String> (Default: 'SIGTERM')

uid <Number> Sets the user identity of the process.

(See setuid(2).)

gid <Number> Sets the group identity of the process.

(See setgid(2).)

callback <Function> called with the output when process terminates

o

error <Error>

stdout <String> | <Buffer>

stderr <String> | <Buffer>

Return: <ChildProcess>

The child_process.execFile() function is similar

to child_process.exec() except that it does not spawn a shell. Rather, the
specified executable file is spawned directly as a new process making it
slightly more efficient than child_process.exec().
The same options as child_process.exec() are supported. Since a shell is
not spawned, behaviors such as I/O redirection and file globbing are not
supported.
const execFile = require('child_process').execFile;
const child = execFile('node', ['--version'], (error, stdout, stderr) => {
if (error) {
throw error;
}
console.log(stdout);
});
The stdout and stderr arguments passed to the callback will contain the
stdout and stderr output of the child process. By default, Node.js will
decode the output as UTF-8 and pass strings to the callback.
The encoding option can be used to specify the character encoding used
to decode the stdout and stderr output.
If encoding is 'buffer', Buffer objects will be passed to the callback instead.
child_process.fork(modulePath[, args][, options])#

modulePath <String> The module to run in the child

args <Array> List of string arguments

options <Object>
o

cwd <String> Current working directory of the child process

env <Object> Environment key-value pairs

execPath <String> Executable used to create the child

process

execArgv <Array> List of string arguments passed to the

executable (Default: process.execArgv)

silent <Boolean> If true, stdin, stdout, and stderr of the child

will be piped to the parent, otherwise they will be inherited from
the parent, see the 'pipe' and 'inherit' options
for child_process.spawn()'s stdio for more details (Default:false)

uid <Number> Sets the user identity of the process.

(See setuid(2).)

gid <Number> Sets the group identity of the process.

(See setgid(2).)

Return: <ChildProcess>

The child_process.fork() method is a special case

of child_process.spawn() used specifically to spawn new Node.js
processes. Likechild_process.spawn(), a ChildProcess object is returned.
The returned ChildProcess will have an additional communication channel
built-in that allows messages to be passed back and forth between the
parent and child. See child.send() for details.
It is important to keep in mind that spawned Node.js child processes are
independent of the parent with exception of the IPC communication
channel that is established between the two. Each process has it's own
memory, with their own V8 instances. Because of the additional resource
allocations required, spawning a large number of child Node.js processes
is not recommended.
By default, child_process.fork() will spawn new Node.js instances using
the process.execPath of the parent process. TheexecPath property in
the options object allows for an alternative execution path to be used.
Node.js processes launched with a custom execPath will communicate
with the parent process using the file descriptor (fd) identified using the
environment variable NODE_CHANNEL_FD on the child process. The input
and output on this fd is expected to be line delimited JSON objects.
Note: Unlike the fork(2) POSIX system call, child_process.fork() does not
clone the current process.
child_process.spawn(command[, args][, options])#

command <String> The command to run

args <Array> List of string arguments

options <Object>

cwd <String> Current working directory of the child process

env <Object> Environment key-value pairs

stdio <Array> | <String> Child's stdio configuration.

(See options.stdio)

detached <Boolean> Prepare child to run independently of its

parent process. Specific behavior depends on the platform,
seeoptions.detached)

uid <Number> Sets the user identity of the process.

(See setuid(2).)

gid <Number> Sets the group identity of the process.

(See setgid(2).)

shell <Boolean> | <String> If true, runs command inside of a

shell. Uses '/bin/sh' on UNIX, and 'cmd.exe' on Windows. A
different shell can be specified as a string. The shell should
understand the -c switch on UNIX, or /s /c on Windows. Defaults
to false (no shell).

return: <ChildProcess>

The child_process.spawn() method spawns a new process using the

given command, with command line arguments in args. If
omitted, args defaults to an empty array.
A third argument may be used to specify additional options, with these
defaults:
{
cwd: undefined,
env: process.env
}
Use cwd to specify the working directory from which the process is
spawned. If not given, the default is to inherit the current working
directory.

Use env to specify environment variables that will be visible to the new
process, the default is process.env.
Example of running ls -lh /usr, capturing stdout, stderr, and the exit code:
const spawn = require('child_process').spawn;
const ls = spawn('ls', ['-lh', '/usr']);
ls.stdout.on('data', (data) => {
console.log(`stdout: ${data}`);
});
ls.stderr.on('data', (data) => {
console.log(`stderr: ${data}`);
});
ls.on('close', (code) => {
console.log(`child process exited with code ${code}`);
});
Example: A very elaborate way to run ps ax | grep ssh
const spawn = require('child_process').spawn;
const ps = spawn('ps', ['ax']);
const grep = spawn('grep', ['ssh']);
ps.stdout.on('data', (data) => {
grep.stdin.write(data);
});
ps.stderr.on('data', (data) => {
console.log(`ps stderr: ${data}`);
});
ps.on('close', (code) => {
if (code !== 0) {
console.log(`ps process exited with code ${code}`);
}
grep.stdin.end();

});
grep.stdout.on('data', (data) => {
console.log(`${data}`);
});
grep.stderr.on('data', (data) => {
console.log(`grep stderr: ${data}`);
});
grep.on('close', (code) => {
if (code !== 0) {
console.log(`grep process exited with code ${code}`);
}
});
Example of checking for failed exec:
const spawn = require('child_process').spawn;
const child = spawn('bad_command');
child.on('error', (err) => {
console.log('Failed to start child process.');
});

options.detached#

On Windows, setting options.detached to true makes it possible for the

child process to continue running after the parent exits. The child will have
its own console window. Once enabled for a child process, it cannot be
disabled.
On non-Windows platforms, if options.detached is set to true, the child
process will be made the leader of a new process group and session. Note
that child processes may continue running after the parent exits
regardless of whether they are detached or not. Seesetsid(2) for more
information.
By default, the parent will wait for the detached child to exit. To prevent
the parent from waiting for a given child, use thechild.unref() method.
Doing so will cause the parent's event loop to not include the child in its

reference count, allowing the parent to exit independently of the child,

unless there is an established IPC channel between the child and parent.
When using the detached option to start a long-running process, the
process will not stay running in the background after the parent exits
unless it is provided with a stdio configuration that is not connected to the
parent. If the parent's stdio is inherited, the child will remain attached to
the controlling terminal.
Example of a long-running process, by detaching and also ignoring its
parent stdio file descriptors, in order to ignore the parent's termination:
const spawn = require('child_process').spawn;
const child = spawn(process.argv[0], ['child_program.js'], {
detached: true,
stdio: ['ignore']
});
child.unref();
Alternatively one can redirect the child process' output into files:
const
const
const
const

fs = require('fs');
spawn = require('child_process').spawn;
out = fs.openSync('./out.log', 'a');
err = fs.openSync('./out.log', 'a');

const child = spawn('prg', [], {

detached: true,
stdio: [ 'ignore', out, err ]
});
child.unref();

options.stdio#

The options.stdio option is used to configure the pipes that are established
between the parent and child process. By default, the child's stdin, stdout,
and stderr are redirected to corresponding child.stdin, child.stdout,

and child.stderr streams on theChildProcess object. This is equivalent to

setting the options.stdio equal to ['pipe', 'pipe', 'pipe'].
For convenience, options.stdio may be one of the following strings:

'pipe' - equivalent to ['pipe', 'pipe', 'pipe'] (the default)

'ignore' - equivalent to ['ignore', 'ignore', 'ignore']

'inherit' - equivalent to [process.stdin, process.stdout,

process.stderr] or [0,1,2]

Otherwise, the value of options.stdio is an array where each index

corresponds to an fd in the child. The fds 0, 1, and 2 correspond to stdin,
stdout, and stderr, respectively. Additional fds can be specified to create
additional pipes between the parent and child. The value is one of the
following:
1.

'pipe' - Create a pipe between the child process and the parent
process. The parent end of the pipe is exposed to the parent as a
property on the child_process object as child.stdio[fd]. Pipes created
for fds 0 - 2 are also available
as child.stdin,child.stdout and child.stderr, respectively.

2.

'ipc' - Create an IPC channel for passing messages/file descriptors

between parent and child. A ChildProcess may have at mostone IPC
stdio file descriptor. Setting this option enables
the child.send() method. If the child writes JSON messages to this file
descriptor, the child.on('message') event handler will be triggered in
the parent. If the child is a Node.js process, the presence of an IPC
channel will
enable process.send(), process.disconnect(), process.on('disconnect'),
and process.on('message')within the child.

3.

'ignore' - Instructs Node.js to ignore the fd in the child. While Node.js

will always open fds 0 - 2 for the processes it spawns, setting the fd
to 'ignore' will cause Node.js to open /dev/null and attach it to the
child's fd.

4.

<Stream> object - Share a readable or writable stream that refers

to a tty, file, socket, or a pipe with the child process. The stream's
underlying file descriptor is duplicated in the child process to the fd
that corresponds to the index in the stdio array. Note that the stream
must have an underlying descriptor (file streams do not until
the 'open' event has occurred).

5.

Positive integer - The integer value is interpreted as a file descriptor

that is is currently open in the parent process. It is shared with the
child process, similar to how <Stream> objects can be shared.

6.

null, undefined - Use default value. For stdio fds 0, 1 and 2 (in other
words, stdin, stdout, and stderr) a pipe is created. For fd 3 and up, the
default is 'ignore'.

Example:
const spawn = require('child_process').spawn;
// Child will use parent's stdios
spawn('prg', [], { stdio: 'inherit' });
// Spawn child sharing only stderr
spawn('prg', [], { stdio: ['pipe', 'pipe', process.stderr] });
// Open an extra fd=4, to interact with programs presenting a
// startd-style interface.
spawn('prg', [], { stdio: ['pipe', null, null, null, 'pipe'] });
It is worth noting that when an IPC channel is established between the
parent and child processes, and the child is a Node.js process, the child is
launched with the IPC channel unreferenced (using unref()) until the child
registers an event handler for the process.on('disconnect')event. This
allows the child to exit normally without the process being held open by
the open IPC channel.
See also: child_process.exec() and child_process.fork()
Synchronous Process Creation#
The child_process.spawnSync(), child_process.execSync(),
and child_process.execFileSync() methods
are synchronous andWILL block the Node.js event loop, pausing
execution of any additional code until the spawned process exits.
Blocking calls like these are mostly useful for simplifying general purpose
scripting tasks and for simplifying the loading/processing of application
configuration at startup.

child_process.execFileSync(file[, args][, options])#

file <String> The name or path of the executable file to run

args <Array> List of string arguments

options <Object>
cwd <String> Current working directory of the child process

o
o

input <String> | <Buffer> The value which will be passed as

stdin to the spawned process

stdio <Array> Child's stdio configuration. (Default: 'pipe')

supplying this value will override stdio[0]

stderr by default will be output to the parent process'

stderr unless stdio is specified
env <Object> Environment key-value pairs

uid <Number> Sets the user identity of the process.

(See setuid(2).)

gid <Number> Sets the group identity of the process.

(See setgid(2).)

timeout <Number> In milliseconds the maximum amount of

time the process is allowed to run. (Default: undefined)

killSignal <String> The signal value to be used when the

spawned process will be killed. (Default: 'SIGTERM')

maxBuffer <Number> largest amount of data (in bytes)

allowed on stdout or stderr - if exceeded child process is killed

encoding <String> The encoding used for all stdio inputs and
outputs. (Default: 'buffer')

return: <Buffer> | <String> The stdout from the command

The child_process.execFileSync() method is generally identical

to child_process.execFile() with the exception that the method will not
return until the child process has fully closed. When a timeout has been
encountered and killSignal is sent, the method won't return until the
process has completely exited. Note that if the child process intercepts

and handles the SIGTERM signal and does not exit, the parent process will
still wait until the child process has exited.
If the process times out, or has a non-zero exit code, this
method will throw. The Error object will contain the entire result
fromchild_process.spawnSync()
child_process.execSync(command[, options])#

command <String> The command to run

options <Object>
cwd <String> Current working directory of the child process

o
o

input <String> | <Buffer> The value which will be passed as

stdin to the spawned process

stdio <Array> Child's stdio configuration. (Default: 'pipe')

supplying this value will override stdio[0]

stderr by default will be output to the parent process'

stderr unless stdio is specified
env <Object> Environment key-value pairs

shell <String> Shell to execute the command with

(Default: '/bin/sh' on UNIX, 'cmd.exe' on Windows, The shell should
understand the -c switch on UNIX or /s /c on Windows. On
Windows, command line parsing should be compatible
withcmd.exe.)

uid <Number> Sets the user identity of the process.

(See setuid(2).)

gid <Number> Sets the group identity of the process.

(See setgid(2).)

timeout <Number> In milliseconds the maximum amount of

time the process is allowed to run. (Default: undefined)

killSignal <String> The signal value to be used when the

spawned process will be killed. (Default: 'SIGTERM')

maxBuffer <Number> largest amount of data (in bytes)

allowed on stdout or stderr - if exceeded child process is killed

encoding <String> The encoding used for all stdio inputs and
outputs. (Default: 'buffer')

return: <Buffer> | <String> The stdout from the command

The child_process.execSync() method is generally identical

to child_process.exec() with the exception that the method will not return
until the child process has fully closed. When a timeout has been
encountered and killSignal is sent, the method won't return until the
process has completely exited. Note that if the child process intercepts
and handles the SIGTERM signal and doesn't exit, the parent process will
wait until the child process has exited.
If the process times out, or has a non-zero exit code, this
method will throw. The Error object will contain the entire result
fromchild_process.spawnSync()
child_process.spawnSync(command[, args][, options])#

command <String> The command to run

args <Array> List of string arguments

options <Object>
cwd <String> Current working directory of the child process

o
o

input <String> | <Buffer> The value which will be passed as

stdin to the spawned process

supplying this value will override stdio[0]

stdio <Array> Child's stdio configuration.

env <Object> Environment key-value pairs

uid <Number> Sets the user identity of the process.

(See setuid(2).)

gid <Number> Sets the group identity of the process.

(See setgid(2).)

timeout <Number> In milliseconds the maximum amount of

time the process is allowed to run. (Default: undefined)

killSignal <String> The signal value to be used when the

spawned process will be killed. (Default: 'SIGTERM')

maxBuffer <Number> largest amount of data (in bytes)

allowed on stdout or stderr - if exceeded child process is killed

encoding <String> The encoding used for all stdio inputs and
outputs. (Default: 'buffer')

shell <Boolean> | <String> If true, runs command inside of a

shell. Uses '/bin/sh' on UNIX, and 'cmd.exe' on Windows. A
different shell can be specified as a string. The shell should
understand the -c switch on UNIX, or /s /c on Windows. Defaults
to false (no shell).

return: <Object>
o

pid <Number> Pid of the child process

output <Array> Array of results from stdio output

stdout <Buffer> | <String> The contents of output[1]

stderr <Buffer> | <String> The contents of output[2]

status <Number> The exit code of the child process

signal <String> The signal used to kill the child process

error <Error> The error object if the child process failed or

timed out

The child_process.spawnSync() method is generally identical

to child_process.spawn() with the exception that the function will not
return until the child process has fully closed. When a timeout has been
encountered and killSignal is sent, the method won't return until the
process has completely exited. Note that if the process intercepts and
handles the SIGTERM signal and doesn't exit, the parent process will wait
until the child process has exited.
Class: ChildProcess#
Instances of the ChildProcess class are EventEmitters that represent
spawned child processes.

Instances of ChildProcess are not intended to be created directly. Rather,

use
the child_process.spawn(), child_process.exec(),child_process.execFile(),
or child_process.fork() methods to create instances of ChildProcess.
Event: 'close'#

code <Number> the exit code if the child exited on its own.
signal <String> the signal by which the child process was
terminated.

The 'close' event is emitted when the stdio streams of a child process
have been closed. This is distinct from the 'exit' event, since multiple
processes might share the same stdio streams.
Event: 'disconnect'#
The 'disconnect' event is emitted after calling
the child.disconnect() method in parent process or process.disconnect() in
child process. After disconnecting it is no longer possible to send or
receive messages, and the child.connected property is false.
Event: 'error'#

err <Error> the error.

The 'error' event is emitted whenever:

1.

The process could not be spawned, or

2.

The process could not be killed, or

3.

Sending a message to the child process failed.

Note that the 'exit' event may or may not fire after an error has occurred.
If you are listening to both the 'exit' and 'error'events, it is important to
guard against accidentally invoking handler functions multiple times.
See also child.kill() and child.send().
Event: 'exit'#

code <Number> the exit code if the child exited on its own.

signal <String> the signal by which the child process was

terminated.

The 'exit' event is emitted after the child process ends. If the process
exited, code is the final exit code of the process, otherwisenull. If the
process terminated due to receipt of a signal, signal is the string name of
the signal, otherwise null. One of the two will always be non-null.
Note that when the 'exit' event is triggered, child process stdio streams
might still be open.
Also, note that Node.js establishes signal handlers
for SIGINT and SIGTERM and Node.js processes will not terminate
immediately due to receipt of those signals. Rather, Node.js will perform a
sequence of cleanup actions and then will re-raise the handled signal.
See waitpid(2).
Event: 'message'#

message <Object> a parsed JSON object or primitive value.

sendHandle <Handle> a net.Socket or net.Server object, or

undefined.

The 'message' event is triggered when a child process

uses process.send() to send messages.
child.connected#

<Boolean> Set to false after child.disconnect() is called

The child.connected property indicates whether it is still possible to send

and receive messages from a child process. Whenchild.connected is false,
it is no longer possible to send or receive messages.
child.disconnect()#
Closes the IPC channel between parent and child, allowing the child to exit
gracefully once there are no other connections keeping it alive. After
calling this method the child.connected and process.connected properties

in both the parent and child (respectively) will be set to false, and it will be
no longer possible to pass messages between the processes.
The 'disconnect' event will be emitted when there are no messages in the
process of being received. This will most often be triggered immediately
after calling child.disconnect().
Note that when the child process is a Node.js instance (e.g. spawned
using child_process.fork()), the process.disconnect() method can be
invoked within the child process to close the IPC channel as well.
child.kill([signal])#

signal <String>

The child.kill() methods sends a signal to the child process. If no argument

is given, the process will be sent the 'SIGTERM' signal. See signal(7) for a
list of available signals.
const spawn = require('child_process').spawn;
const grep = spawn('grep', ['ssh']);
grep.on('close', (code, signal) => {
console.log(
`child process terminated due to receipt of signal ${signal}`);
});
// Send SIGHUP to process
grep.kill('SIGHUP');
The ChildProcess object may emit an 'error' event if the signal cannot be
delivered. Sending a signal to a child process that has already exited is
not an error but may have unforeseen consequences. Specifically, if the
process identifier (PID) has been reassigned to another process, the signal
will be delivered to that process instead which can have unexpected
results.
Note that while the function is called kill, the signal delivered to the child
process may not actually terminate the process.
See kill(2) for reference.

Also note: on Linux, child processes of child processes will not be

terminated when attempting to kill their parent. This is likely to happen
when running a new process in a shell or with use of the shell option
of ChildProcess, such as in this example:
'use strict';
const spawn = require('child_process').spawn;
let child = spawn('sh', ['-c',
`node -e "setInterval(() => {
console.log(process.pid + 'is alive')
}, 500);"`
], {
stdio: ['inherit', 'inherit', 'inherit']
});
setTimeout(() => {
child.kill(); // does not terminate the node process in the shell
}, 2000);
child.pid#

<Number> Integer

Returns the process identifier (PID) of the child process.

Example:
const spawn = require('child_process').spawn;
const grep = spawn('grep', ['ssh']);
console.log(`Spawned child pid: ${grep.pid}`);
grep.stdin.end();
child.send(message[, sendHandle[, options]][, callback])#

message <Object>

sendHandle <Handle>

options <Object>

callback <Function>

Return: <Boolean>

When an IPC channel has been established between the parent and child (
i.e. when using child_process.fork()), the child.send()method can be used
to send messages to the child process. When the child process is a Node.js
instance, these messages can be received via
the process.on('message') event.
For example, in the parent script:
const cp = require('child_process');
const n = cp.fork(`${__dirname}/sub.js`);
n.on('message', (m) => {
console.log('PARENT got message:', m);
});
n.send({ hello: 'world' });
And then the child script, 'sub.js' might look like this:
process.on('message', (m) => {
console.log('CHILD got message:', m);
});
process.send({ foo: 'bar' });
Child Node.js processes will have a process.send() method of their own
that allows the child to send messages back to the parent.
There is a special case when sending a {cmd: 'NODE_foo'} message. All
messages containing a NODE_ prefix in its cmd property are considered to
be reserved for use within Node.js core and will not be emitted in the
child's process.on('message') event. Rather, such messages are emitted
using the process.on('internalMessage') event and are consumed
internally by Node.js. Applications should avoid using such messages or
listening for 'internalMessage' events as it is subject to change without
notice.

The optional sendHandle argument that may be passed to child.send() is

for passing a TCP server or socket object to the child process. The child
will receive the object as the second argument passed to the callback
function registered on theprocess.on('message') event.
The options argument, if present, is an object used to parameterize the
sending of certain types of handles. options supports the following
properties:

keepOpen - A Boolean value that can be used when passing

instances of net.Socket. When true, the socket is kept open in the
sending process. Defaults to false.

The optional callback is a function that is invoked after the message is

sent but before the child may have received it. The function is called with
a single argument: null on success, or an Error object on failure.
If no callback function is provided and the message cannot be sent,
an 'error' event will be emitted by the ChildProcess object. This can
happen, for instance, when the child process has already exited.
child.send() will return false if the channel has closed or when the backlog
of unsent messages exceeds a threshold that makes it unwise to send
more. Otherwise, the method returns true. The callback function can be
used to implement flow control.
Example: sending a server object#

The sendHandle argument can be used, for instance, to pass the handle of
a TCP server object to the child process as illustrated in the example
below:
const child = require('child_process').fork('child.js');
// Open up the server object and send the handle.
const server = require('net').createServer();
server.on('connection', (socket) => {
socket.end('handled by parent');
});
server.listen(1337, () => {
child.send('server', server);

});
The child would then receive the server object as:
process.on('message', (m, server) => {
if (m === 'server') {
server.on('connection', (socket) => {
socket.end('handled by child');
});
}
});
Once the server is now shared between the parent and child, some
connections can be handled by the parent and some by the child.
While the example above uses a server created using
the net module, dgram module servers use exactly the same workflow
with the exceptions of listening on a 'message' event instead
of 'connection' and using server.bind() instead of server.listen(). This is,
however, currently only supported on UNIX platforms.
Example: sending a socket object#

Similarly, the sendHandler argument can be used to pass the handle of a

socket to the child process. The example below spawns two children that
each handle connections with "normal" or "special" priority:
const normal = require('child_process').fork('child.js', ['normal']);
const special = require('child_process').fork('child.js', ['special']);
// Open up the server and send sockets to child
const server = require('net').createServer();
server.on('connection', (socket) => {
// If this is special priority
if (socket.remoteAddress === '74.125.127.100') {
special.send('socket', socket);
return;
}
// This is normal priority

normal.send('socket', socket);
});
server.listen(1337);
The child.js would receive the socket handle as the second argument
passed to the event callback function:
process.on('message', (m, socket) => {
if (m === 'socket') {
socket.end(`Request handled with ${process.argv[2]} priority`);
}
});
Once a socket has been passed to a child, the parent is no longer capable
of tracking when the socket is destroyed. To indicate this,
the.connections property becomes null. It is recommended not to
use .maxConnections when this occurs.
Note: this function uses JSON.stringify() internally to serialize
the message.
child.stderr#

<Stream>

A Readable Stream that represents the child process's stderr.

If the child was spawned with stdio[2] set to anything other than 'pipe',
then this will be undefined.
child.stderr is an alias for child.stdio[2]. Both properties will refer to the
same value.
child.stdin#

<Stream>

A Writable Stream that represents the child process's stdin.

Note that if a child process waits to read all of its input, the child will not
continue until this stream has been closed via end().

If the child was spawned with stdio[0] set to anything other than 'pipe',
then this will be undefined.
child.stdin is an alias for child.stdio[0]. Both properties will refer to the
same value.
child.stdio#

<Array>

A sparse array of pipes to the child process, corresponding with positions

in the stdio option passed to child_process.spawn() that have been set to
the value 'pipe'. Note that child.stdio[0], child.stdio[1],
and child.stdio[2] are also available aschild.stdin, child.stdout,
and child.stderr, respectively.
In the following example, only the child's fd 1 (stdout) is configured as a
pipe, so only the parent's child.stdio[1] is a stream, all other values in the
array are null.
const assert = require('assert');
const fs = require('fs');
const child_process = require('child_process');
const child = child_process.spawn('ls', {
stdio: [
0, // Use parents stdin for child
'pipe', // Pipe child's stdout to parent
fs.openSync('err.out', 'w') // Direct child's stderr to a file
]
});
assert.equal(child.stdio[0], null);
assert.equal(child.stdio[0], child.stdin);
assert(child.stdout);
assert.equal(child.stdio[1], child.stdout);
assert.equal(child.stdio[2], null);
assert.equal(child.stdio[2], child.stderr);

child.stdout#

<Stream>

A Readable Stream that represents the child process's stdout.

If the child was spawned with stdio[1] set to anything other than 'pipe',
then this will be undefined.
child.stdout is an alias for child.stdio[1]. Both properties will refer to the
same value.
maxBuffer and Unicode#
It is important to keep in mind that the maxBuffer option specifies the
largest number of octets allowed on stdout or stderr. If this value is
exceeded, then the child process is terminated. This particularly impacts
output that includes multibyte character encodings such as UTF-8 or UTF16. For instance, the following will output 13 UTF-8 encoded octets
to stdout although there are only 4 characters:
console.log('');

Cluster

How It Works

Class: Worker

Event: 'disconnect'

Event: 'error'

Event: 'exit'

Event: 'listening'

Event: 'message'

Event: 'online'

worker.disconnect()

worker.exitedAfterDisconnect

worker.id

worker.isConnected()

worker.isDead()

worker.kill([signal='SIGTERM'])

worker.process

worker.send(message[, sendHandle][, callback])

worker.suicide

Event: 'disconnect'

Event: 'exit'

Event: 'fork'

Event: 'listening'

Event: 'message'

Event: 'online'

Event: 'setup'

cluster.disconnect([callback])

cluster.fork([env])

cluster.isMaster

cluster.isWorker

cluster.schedulingPolicy

cluster.settings

cluster.setupMaster([settings])

cluster.worker


Cluster#

cluster.workers

Stability: 2 - Stable
A single instance of Node.js runs in a single thread. To take advantage of
multi-core systems the user will sometimes want to launch a cluster of
Node.js processes to handle the load.
The cluster module allows you to easily create child processes that all
share server ports.
const cluster = require('cluster');
const http = require('http');
const numCPUs = require('os').cpus().length;
if (cluster.isMaster) {
// Fork workers.
for (var i = 0; i < numCPUs; i++) {
cluster.fork();
}
cluster.on('exit', (worker, code, signal) => {
console.log(`worker ${worker.process.pid} died`);
});
} else {
// Workers can share any TCP connection
// In this case it is an HTTP server
http.createServer((req, res) => {
res.writeHead(200);
res.end('hello world\n');
}).listen(8000);
}
Running Node.js will now share port 8000 between the workers:
$ NODE_DEBUG=cluster node server.js
23521,Master Worker 23524 online
23521,Master Worker 23526 online
23521,Master Worker 23523 online

23521,Master Worker 23528 online

Please note that, on Windows, it is not yet possible to set up a named pipe
server in a worker.
How It Works#
The worker processes are spawned using the child_process.fork() method,
so that they can communicate with the parent via IPC and pass server
handles back and forth.
The cluster module supports two methods of distributing incoming
connections.
The first one (and the default one on all platforms except Windows), is the
round-robin approach, where the master process listens on a port, accepts
new connections and distributes them across the workers in a round-robin
fashion, with some built-in smarts to avoid overloading a worker process.
The second approach is where the master process creates the listen
socket and sends it to interested workers. The workers then accept
incoming connections directly.
The second approach should, in theory, give the best performance. In
practice however, distribution tends to be very unbalanced due to
operating system scheduler vagaries. Loads have been observed where
over 70% of all connections ended up in just two processes, out of a total
of eight.
Because server.listen() hands off most of the work to the master process,
there are three cases where the behavior between a normal Node.js
process and a cluster worker differs:
1.

server.listen({fd: 7}) Because the message is passed to the master,

file descriptor 7 in the parent will be listened on, and the handle
passed to the worker, rather than listening to the worker's idea of
what the number 7 file descriptor references.

2.

server.listen(handle) Listening on handles explicitly will cause the

worker to use the supplied handle, rather than talk to the master
process. If the worker already has the handle, then it's presumed that
you know what you are doing.

3.

server.listen(0) Normally, this will cause servers to listen on a

random port. However, in a cluster, each worker will receive the same
"random" port each time they do listen(0). In essence, the port is
random the first time, but predictable thereafter. If you want to listen
on a unique port, generate a port number based on the cluster worker
ID.

There is no routing logic in Node.js, or in your program, and no shared

state between the workers. Therefore, it is important to design your
program such that it does not rely too heavily on in-memory data objects
for things like sessions and login.
Because workers are all separate processes, they can be killed or respawned depending on your program's needs, without affecting other
workers. As long as there are some workers still alive, the server will
continue to accept connections. If no workers are alive, existing
connections will be dropped and new connections will be refused. Node.js
does not automatically manage the number of workers for you, however. It
is your responsibility to manage the worker pool for your application's
needs.
Class: Worker#
A Worker object contains all public information and method about a
worker. In the master it can be obtained using cluster.workers. In a worker
it can be obtained using cluster.worker.
Event: 'disconnect'#
Similar to the cluster.on('disconnect') event, but specific to this worker.
cluster.fork().on('disconnect', () => {
// Worker has disconnected
});
Event: 'error'#
This event is the same as the one provided by child_process.fork().
In a worker you can also use process.on('error').
Event: 'exit'#

code <Number> the exit code, if it exited normally.

signal <String> the name of the signal (eg. 'SIGHUP') that caused
the process to be killed.

Similar to the cluster.on('exit') event, but specific to this worker.

const worker = cluster.fork();
worker.on('exit', (code, signal) => {
if (signal) {
console.log(`worker was killed by signal: ${signal}`);
} else if (code !== 0) {
console.log(`worker exited with error code: ${code}`);
} else {
console.log('worker success!');
}
});
Event: 'listening'#

address <Object>

Similar to the cluster.on('listening') event, but specific to this worker.

cluster.fork().on('listening', (address) => {
// Worker is listening
});
It is not emitted in the worker.
Event: 'message'#

message <Object>

Similar to the cluster.on('message') event, but specific to this worker.

This event is the same as the one provided by child_process.fork().
In a worker you can also use process.on('message').
As an example, here is a cluster that keeps count of the number of
requests in the master process using the message system:
const cluster = require('cluster');
const http = require('http');

if (cluster.isMaster) {
// Keep track of http requests
var numReqs = 0;
setInterval(() => {
console.log('numReqs =', numReqs);
}, 1000);
// Count requests
function messageHandler(msg) {
if (msg.cmd && msg.cmd == 'notifyRequest') {
numReqs += 1;
}
}
// Start workers and listen for messages containing notifyRequest
const numCPUs = require('os').cpus().length;
for (var i = 0; i < numCPUs; i++) {
cluster.fork();
}
Object.keys(cluster.workers).forEach((id) => {
cluster.workers[id].on('message', messageHandler);
});
} else {
// Worker processes have a http server.
http.Server((req, res) => {
res.writeHead(200);
res.end('hello world\n');
// notify master about the request
process.send({ cmd: 'notifyRequest' });
}).listen(8000);
}

Event: 'online'#
Similar to the cluster.on('online') event, but specific to this worker.
cluster.fork().on('online', () => {
// Worker is online
});
It is not emitted in the worker.
worker.disconnect()#
In a worker, this function will close all servers, wait for the 'close' event on
those servers, and then disconnect the IPC channel.
In the master, an internal message is sent to the worker causing it to
call .disconnect() on itself.
Causes .exitedAfterDisconnect to be set.
Note that after a server is closed, it will no longer accept new connections,
but connections may be accepted by any other listening worker. Existing
connections will be allowed to close as usual. When no more connections
exist, see server.close(), the IPC channel to the worker will close allowing
it to die gracefully.
The above applies only to server connections, client connections are not
automatically closed by workers, and disconnect does not wait for them to
close before exiting.
Note that in a worker, process.disconnect exists, but it is not this function,
it is disconnect.
Because long living server connections may block workers from
disconnecting, it may be useful to send a message, so application specific
actions may be taken to close them. It also may be useful to implement a
timeout, killing a worker if the 'disconnect' event has not been emitted
after some time.
if (cluster.isMaster) {
var worker = cluster.fork();

var timeout;
worker.on('listening', (address) => {
worker.send('shutdown');
worker.disconnect();
timeout = setTimeout(() => {
worker.kill();
}, 2000);
});
worker.on('disconnect', () => {
clearTimeout(timeout);
});
} else if (cluster.isWorker) {
const net = require('net');
var server = net.createServer((socket) => {
// connections never end
});
server.listen(8000);
process.on('message', (msg) => {
if (msg === 'shutdown') {
// initiate graceful close of any connections to server
}
});
}
worker.exitedAfterDisconnect#

<Boolean>

Set by calling .kill() or .disconnect(). Until then, it is undefined.

The boolean worker.exitedAfterDisconnect lets you distinguish between
voluntary and accidental exit, the master may choose not to respawn a
worker based on this value.
cluster.on('exit', (worker, code, signal) => {

if (worker.exitedAfterDisconnect === true) {

console.log('Oh, it was just voluntary no need to worry');
}
});
// kill worker
worker.kill();
worker.id#

<Number>

Each new worker is given its own unique id, this id is stored in the id.
While a worker is alive, this is the key that indexes it in cluster.workers
worker.isConnected()#
This function returns true if the worker is connected to its master via its
IPC channel, false otherwise. A worker is connected to its master after it's
been created. It is disconnected after the 'disconnect' event is emitted.
worker.isDead()#
This function returns true if the worker's process has terminated (either
because of exiting or being signaled). Otherwise, it returnsfalse.
worker.kill([signal='SIGTERM'])#

signal <String> Name of the kill signal to send to the worker

process.

This function will kill the worker. In the master, it does this by
disconnecting the worker.process, and once disconnected, killing
withsignal. In the worker, it does it by disconnecting the channel, and then
exiting with code 0.
Causes .exitedAfterDisconnect to be set.
This method is aliased as worker.destroy() for backwards compatibility.
Note that in a worker, process.kill() exists, but it is not this function, it
is kill.

worker.process#

<ChildProcess>

All workers are created using child_process.fork(), the returned object from
this function is stored as .process. In a worker, the global process is
stored.
See: Child Process module
Note that workers will call process.exit(0) if the 'disconnect' event occurs
on process and .exitedAfterDisconnect is nottrue. This protects against
accidental disconnection.
worker.send(message[, sendHandle][, callback])#

message <Object>

sendHandle <Handle>

callback <Function>

Return: Boolean

Send a message to a worker or master, optionally with a handle.

In the master this sends a message to a specific worker. It is identical
to ChildProcess.send().
In a worker this sends a message to the master. It is identical
to process.send().
This example will echo back all messages from the master:
if (cluster.isMaster) {
var worker = cluster.fork();
worker.send('hi there');
} else if (cluster.isWorker) {
process.on('message', (msg) => {
process.send(msg);
});

}
worker.suicide#
Stability: 0 - Deprecated: Use worker.exitedAfterDisconnect instead.
An alias to worker.exitedAfterDisconnect.
Set by calling .kill() or .disconnect(). Until then, it is undefined.
The boolean worker.suicide lets you distinguish between voluntary and
accidental exit, the master may choose not to respawn a worker based on
this value.
cluster.on('exit', (worker, code, signal) => {
if (worker.suicide === true) {
console.log('Oh, it was just voluntary no need to worry');
}
});
// kill worker
worker.kill();
This API only exists for backwards compatibility and will be removed in the
future.
Event: 'disconnect'#

worker <cluster.Worker>

Emitted after the worker IPC channel has disconnected. This can occur
when a worker exits gracefully, is killed, or is disconnected manually (such
as with worker.disconnect()).
There may be a delay between the 'disconnect' and 'exit' events. These
events can be used to detect if the process is stuck in a cleanup or if there
are long-living connections.
cluster.on('disconnect', (worker) => {
console.log(`The worker #${worker.id} has disconnected`);
});
Event: 'exit'#

worker <cluster.Worker>

code <Number> the exit code, if it exited normally.

signal <String> the name of the signal (eg. 'SIGHUP') that caused
the process to be killed.

When any of the workers die the cluster module will emit the 'exit' event.
This can be used to restart the worker by calling .fork() again.
cluster.on('exit', (worker, code, signal) => {
console.log('worker %d died (%s). restarting...',
worker.process.pid, signal || code);
cluster.fork();
});
See child_process event: 'exit'.
Event: 'fork'#

worker <cluster.Worker>

When a new worker is forked the cluster module will emit a 'fork' event.
This can be used to log worker activity, and create your own timeout.
var timeouts = [];
function errorMsg() {
console.error('Something must be wrong with the connection ...');
}
cluster.on('fork', (worker) => {
timeouts[worker.id] = setTimeout(errorMsg, 2000);
});
cluster.on('listening', (worker, address) => {
clearTimeout(timeouts[worker.id]);
});
cluster.on('exit', (worker, code, signal) => {
clearTimeout(timeouts[worker.id]);
errorMsg();
});

Event: 'listening'#

worker <cluster.Worker>

address <Object>

After calling listen() from a worker, when the 'listening' event is emitted on
the server, a 'listening' event will also be emitted on cluster in the master.
The event handler is executed with two arguments, the worker contains
the worker object and the address object contains the following
connection properties: address, port and addressType. This is very useful if
the worker is listening on more than one address.
cluster.on('listening', (worker, address) => {
console.log(
`A worker is now connected to ${address.address}:$
{address.port}`);
});
The addressType is one of:

4 (TCPv4)

6 (TCPv6)

-1 (unix domain socket)

"udp4" or "udp6" (UDP v4 or v6)

Event: 'message'#

worker <cluster.Worker>

message <Object>

handle <undefined> | <Object>

Emitted when any worker receives a message.

See child_process event: 'message'.

Before Node.js v6.0, this event emitted only the message and the handle,
but not the worker object, contrary to what the documentation stated.
If you need to support older versions and don't need the worker object,
you can work around the discrepancy by checking the number of
arguments:
cluster.on('message', function(worker, message, handle) {
if (arguments.length === 2) {
handle = message;
message = worker;
worker = undefined;
}
// ...
});
Event: 'online'#

worker <cluster.Worker>

After forking a new worker, the worker should respond with an online
message. When the master receives an online message it will emit this
event. The difference between 'fork' and 'online' is that fork is emitted
when the master forks a worker, and 'online' is emitted when the worker is
running.
cluster.on('online', (worker) => {
console.log('Yay, the worker responded after it was forked');
});
Event: 'setup'#

settings <Object>

Emitted every time .setupMaster() is called.

The settings object is the cluster.settings object at the
time .setupMaster() was called and is advisory only, since multiple calls
to .setupMaster() can be made in a single tick.
If accuracy is important, use cluster.settings.

cluster.disconnect([callback])#

callback <Function> called when all workers are disconnected and

handles are closed

Calls .disconnect() on each worker in cluster.workers.

When they are disconnected all internal handles will be closed, allowing
the master process to die gracefully if no other event is waiting.
The method takes an optional callback argument which will be called
when finished.
This can only be called from the master process.
cluster.fork([env])#

env <Object> Key/value pairs to add to worker process

environment.
return <cluster.Worker>

Spawn a new worker process.

This can only be called from the master process.
cluster.isMaster#

<Boolean>

True if the process is a master. This is determined by

the process.env.NODE_UNIQUE_ID. If process.env.NODE_UNIQUE_ID is
undefined, then isMaster is true.
cluster.isWorker#

<Boolean>

True if the process is not a master (it is the negation of cluster.isMaster).

cluster.schedulingPolicy#
The scheduling policy, either cluster.SCHED_RR for round-robin
or cluster.SCHED_NONE to leave it to the operating system. This is a

global setting and effectively frozen once you spawn the first worker or
call cluster.setupMaster(), whatever comes first.
SCHED_RR is the default on all operating systems except Windows.
Windows will change to SCHED_RR once libuv is able to effectively
distribute IOCP handles without incurring a large performance hit.
cluster.schedulingPolicy can also be set through
the NODE_CLUSTER_SCHED_POLICY environment variable. Valid values
are "rr"and "none".
cluster.settings#

<Object>
o

execArgv <Array> list of string arguments passed to the

Node.js executable. (Default=process.execArgv)

exec <String> file path to worker file.

(Default=process.argv[1])

args <Array> string arguments passed to worker.

(Default=process.argv.slice(2))

silent <Boolean> whether or not to send output to parent's

stdio. (Default=false)

uid <Number> Sets the user identity of the process.

(See setuid(2).)

gid <Number> Sets the group identity of the process.

(See setgid(2).)

After calling .setupMaster() (or .fork()) this settings object will contain the
settings, including the default values.
It is effectively frozen after being set, because .setupMaster() can only be
called once.
This object is not supposed to be changed or set manually, by you.
cluster.setupMaster([settings])#

settings <Object>

exec <String> file path to worker file.

(Default=process.argv[1])

args <Array> string arguments passed to worker.

(Default=process.argv.slice(2))

silent <Boolean> whether or not to send output to parent's

stdio. (Default=false)

setupMaster is used to change the default 'fork' behavior. Once called, the
settings will be present in cluster.settings.
Note that:

any settings changes only affect future calls to .fork() and have no
effect on workers that are already running

The only attribute of a worker that cannot be set

via .setupMaster() is the env passed to .fork()

the defaults above apply to the first call only, the defaults for later
calls is the current value at the time of cluster.setupMaster()is called

Example:
const cluster = require('cluster');
cluster.setupMaster({
exec: 'worker.js',
args: ['--use', 'https'],
silent: true
});
cluster.fork(); // https worker
cluster.setupMaster({
exec: 'worker.js',
args: ['--use', 'http']
});
cluster.fork(); // http worker
This can only be called from the master process.
cluster.worker#

<Object>

A reference to the current worker object. Not available in the master

process.
const cluster = require('cluster');
if (cluster.isMaster) {
console.log('I am master');
cluster.fork();
cluster.fork();
} else if (cluster.isWorker) {
console.log(`I am worker #${cluster.worker.id}`);
}
cluster.workers#

<Object>

A hash that stores the active worker objects, keyed by id field. Makes it
easy to loop through all the workers. It is only available in the master
process.
A worker is removed from cluster.workers after the worker has
disconnected and exited. The order between these two events cannot be
determined in advance. However, it is guaranteed that the removal from
the cluster.workers list happens before last 'disconnect'or 'exit' event is
emitted.
// Go through all workers
function eachWorker(callback) {
for (var id in cluster.workers) {
callback(cluster.workers[id]);
}
}
eachWorker((worker) => {
worker.send('big announcement to all workers');
});
Should you wish to reference a worker over a communication channel,
using the worker's unique id is the easiest way to find the worker.

socket.on('data', (id) => {

var worker = cluster.workers[id];
});
Command Line Options#
Node.js comes with a wide variety of CLI options. These options expose
built-in debugging, multiple ways to execute scripts, and other helpful
runtime options.
To view this documentation as a manual page in your terminal, run man
node.
Synopsis#
node [options] [v8 options] [script.js | -e "script"] [arguments]
node debug [script.js | -e "script" | <host>:<port>]
node --v8-options
Execute without arguments to start the REPL.
For more info about node debug, please see the debugger documentation.
Options#
-v, --version#
Print node's version.
-h, --help#
Print node command line options. The output of this option is less detailed
than this document.
-e, --eval "script"#
Evaluate the following argument as JavaScript. The modules which are
predefined in the REPL can also be used in script.

-p, --print "script"#

Identical to -e but prints the result.
-c, --check#
Syntax check the script without executing.
-i, --interactive#
Opens the REPL even if stdin does not appear to be a terminal.
-r, --require module#
Preload the specified module at startup.
Follows require()'s module resolution rules. module may be either a path
to a file, or a node module name.
--no-deprecation#
Silence deprecation warnings.
--trace-deprecation#
Print stack traces for deprecations.
--throw-deprecation#
Throw errors for deprecations.
--no-warnings#
Silence all process warnings (including deprecations).
--trace-warnings#
Print stack traces for process warnings (including deprecations).
--trace-sync-io#
Prints a stack trace whenever synchronous I/O is detected after the first
turn of the event loop.

--zero-fill-buffers#
Automatically zero-fills all newly
allocated Buffer and SlowBuffer instances.
--preserve-symlinks#
Instructs the module loader to preserve symbolic links when resolving and
caching modules.
By default, when Node.js loads a module from a path that is symbolically
linked to a different on-disk location, Node.js will dereference the link and
use the actual on-disk "real path" of the module as both an identifier and
as a root path to locate other dependency modules. In most cases, this
default behavior is acceptable. However, when using symbolically linked
peer dependencies, as illustrated in the example below, the default
behavior causes an exception to be thrown if moduleA attempts to
require moduleB as a peer dependency:
{appDir}
app
index.js
node_modules

moduleA -> {appDir}/moduleA

moduleB

index.js

package.json
moduleA
index.js
package.json
The --preserve-symlinks command line flag instructs Node.js to use the
symlink path for modules as opposed to the real path, allowing
symbolically linked peer dependencies to be found.
Note, however, that using --preserve-symlinks can have other side effects.
Specifically, symbolically linked native modules can fail to load if those are
linked from more than one location in the dependency tree (Node.js would
see those as two separate modules and would attempt to load the module
multiple times, causing an exception to be thrown).

--track-heap-objects#
Track heap object allocations for heap snapshots.
--prof-process#
Process v8 profiler output generated using the v8 option --prof.
--v8-options#
Print v8 command line options.
Note: v8 options allow words to be separated by both dashes (-) or
underscores (_).
For example, --stack-trace-limit is equivalent to --stack_trace_limit.
--tls-cipher-list=list#
Specify an alternative default TLS cipher list. (Requires Node.js to be built
with crypto support. (Default))
--enable-fips#
Enable FIPS-compliant crypto at startup. (Requires Node.js to be built
with ./configure --openssl-fips)
--force-fips#
Force FIPS-compliant crypto on startup. (Cannot be disabled from script
code.) (Same requirements as --enable-fips)
--icu-data-dir=file#
Specify ICU data load path. (overrides NODE_ICU_DATA)
Environment Variables#
NODE_DEBUG=module[,]#
','-separated list of core modules that should print debug information.

NODE_PATH=path[:]#
':'-separated list of directories prefixed to the module search path.
Note: on Windows, this is a ';'-separated list instead.
NODE_DISABLE_COLORS=1#
When set to 1 colors will not be used in the REPL.
NODE_ICU_DATA=file#
Data path for ICU (Intl object) data. Will extend linked-in data when
compiled with small-icu support.
NODE_REPL_HISTORY=file#
Path to the file used to store the persistent REPL history. The default path
is ~/.node_repl_history, which is overridden by this variable. Setting the
value to an empty string ("" or " ") disables persistent REPL history.

Console

Asynchronous vs Synchronous Consoles

Class: Console

new Console(stdout[, stderr])

console.assert(value[, message][, ...])

console.dir(obj[, options])

console.error([data][, ...])

console.info([data][, ...])

console.log([data][, ...])

console.time(label)

console.timeEnd(label)

Console#

console.trace(message[, ...])
console.warn([data][, ...])

Stability: 2 - Stable
The console module provides a simple debugging console that is similar to
the JavaScript console mechanism provided by web browsers.
The module exports two specific components:

A Console class with methods such

as console.log(), console.error() and console.warn() that can be used
to write to any Node.js stream.

A global console instance configured to write to stdout and stderr.

Because this object is global, it can be used without
callingrequire('console').

Example using the global console:

console.log('hello world');
// Prints: hello world, to stdout
console.log('hello %s', 'world');
// Prints: hello world, to stdout
console.error(new Error('Whoops, something bad happened'));
// Prints: [Error: Whoops, something bad happened], to stderr
const name = 'Will Robinson';
console.warn(`Danger ${name}! Danger!`);
// Prints: Danger Will Robinson! Danger!, to stderr
Example using the Console class:
const out = getStreamSomehow();
const err = getStreamSomehow();
const myConsole = new console.Console(out, err);
myConsole.log('hello world');
// Prints: hello world, to out
myConsole.log('hello %s', 'world');

// Prints: hello world, to out

myConsole.error(new Error('Whoops, something bad happened'));
// Prints: [Error: Whoops, something bad happened], to err
const name = 'Will Robinson';
myConsole.warn(`Danger ${name}! Danger!`);
// Prints: Danger Will Robinson! Danger!, to err
While the API for the Console class is designed fundamentally around the
browser console object, the Console in Node.js is not intended to duplicate
the browser's functionality exactly.
Asynchronous vs Synchronous Consoles#
The console functions are asynchronous unless the destination is a file.
Disks are fast and operating systems normally employ write-back caching;
it should be a very rare occurrence indeed that a write blocks, but it is
possible.
Class: Console#
The Console class can be used to create a simple logger with configurable
output streams and can be accessed using
either require('console').Consoleor console.Console:
const Console = require('console').Console;
const Console = console.Console;
new Console(stdout[, stderr])#
Creates a new Console by passing one or two writable stream
instances. stdout is a writable stream to print log or info output. stderr is
used for warning or error output. If stderr isn't passed, warning and error
output will be sent to stdout.
const output = fs.createWriteStream('./stdout.log');
const errorOutput = fs.createWriteStream('./stderr.log');
// custom simple logger
const logger = new Console(output, errorOutput);
// use it like console
var count = 5;

logger.log('count: %d', count);

// in stdout.log: count 5
The global console is a special Console whose output is sent
to process.stdout and process.stderr. It is equivalent to calling:
new Console(process.stdout, process.stderr);
console.assert(value[, message][, ...])#
A simple assertion test that verifies whether value is truthy. If it is not,
an AssertionError is thrown. If provided, the error message is formatted
usingutil.format() and used as the error message.
console.assert(true, 'does nothing');
// OK
console.assert(false, 'Whoops %s', 'didn\'t work');
// AssertionError: Whoops didn't work
Note: the console.assert() method is implemented differently in Node.js
than the console.assert() method available in browsers.
Specifically, in browsers, calling console.assert() with a falsy assertion will
cause the message to be printed to the console without interrupting
execution of subsequent code. In Node.js, however, a falsy assertion will
cause an AssertionError to be thrown.
Functionality approximating that implemented by browsers can be
implemented by extending Node.js' console and overriding
the console.assert()method.
In the following example, a simple module is created that extends and
overrides the default behavior of console in Node.js.
'use strict';
// Creates a simple extension of console with a
// new impl for assert without monkey-patching.
const myConsole = Object.setPrototypeOf({
assert(assertion, message, ...args) {
try {

console.assert(assertion, message, ...args);

} catch (err) {
console.error(err.stack);
}
}
}, console);
module.exports = myConsole;
This can then be used as a direct replacement for the built in console:
const console = require('./myConsole');
console.assert(false, 'this message will print, but no error thrown');
console.log('this will also print');
console.dir(obj[, options])#
Uses util.inspect() on obj and prints the resulting string to stdout. This
function bypasses any custom inspect() function defined on obj. An
optional options object may be passed to alter certain aspects of the
formatted string:

showHidden - if true then the object's non-enumerable and symbol

properties will be shown too. Defaults to false.

depth - tells util.inspect() how many times to recurse while

formatting the object. This is useful for inspecting large complicated
objects. Defaults to 2. To make it recurse indefinitely, pass null.

colors - if true, then the output will be styled with ANSI color codes.
Defaults to false. Colors are customizable;
see customizing util.inspect()colors.

console.error([data][, ...])#
Prints to stderr with newline. Multiple arguments can be passed, with the
first used as the primary message and all additional used as substitution
values similar to printf(3) (the arguments are all passed to util.format()).
const code = 5;
console.error('error #%d', code);

// Prints: error #5, to stderr

console.error('error', code);
// Prints: error 5, to stderr
If formatting elements (e.g. %d) are not found in the first string
then util.inspect() is called on each argument and the resulting string
values are concatenated. See util.format() for more information.
console.info([data][, ...])#
The console.info() function is an alias for console.log().
console.log([data][, ...])#
Prints to stdout with newline. Multiple arguments can be passed, with the
first used as the primary message and all additional used as substitution
values similar to printf(3) (the arguments are all passed to util.format()).
var count = 5;
console.log('count: %d', count);
// Prints: count: 5, to stdout
console.log('count: ', count);
// Prints: count: 5, to stdout
If formatting elements (e.g. %d) are not found in the first string
then util.inspect() is called on each argument and the resulting string
values are concatenated. See util.format() for more information.
console.time(label)#
Starts a timer that can be used to compute the duration of an operation.
Timers are identified by a unique label. Use the same label when you
callconsole.timeEnd() to stop the timer and output the elapsed time in
milliseconds to stdout. Timer durations are accurate to the submillisecond.
console.timeEnd(label)#
Stops a timer that was previously started by calling console.time() and
prints the result to stdout:

console.time('100-elements');
for (var i = 0; i < 100; i++) {
;
}
console.timeEnd('100-elements');
// prints 100-elements: 225.438ms
Note: As of Node.js v6.0.0, console.timeEnd() deletes the timer to avoid
leaking it. On older versions, the timer persisted. This
allowed console.timeEnd() to be called multiple times for the same label.
This functionality was unintended and is no longer supported.
console.trace(message[, ...])#
Prints to stderr the string 'Trace :', followed by the util.format() formatted
message and stack trace to the current position in the code.
console.trace('Show me');
// Prints: (stack trace will vary based on where trace is called)
// Trace: Show me
// at repl:2:9
// at REPLServer.defaultEval (repl.js:248:27)
// at bound (domain.js:287:14)
// at REPLServer.runBound [as eval] (domain.js:300:12)
// at REPLServer.<anonymous> (repl.js:412:12)
// at emitOne (events.js:82:20)
// at REPLServer.emit (events.js:169:7)
// at REPLServer.Interface._onLine (readline.js:210:10)
// at REPLServer.Interface._line (readline.js:549:8)
// at REPLServer.Interface._ttyWrite (readline.js:826:14)
console.warn([data][, ...])#
The console.warn() function is an alias for console.error().

Crypto

Determining if crypto support is unavailable

Class: Certificate

new crypto.Certificate()

certificate.exportChallenge(spkac)

certificate.exportPublicKey(spkac)

certificate.verifySpkac(spkac)
Class: Cipher

cipher.final([output_encoding])

cipher.setAAD(buffer)

cipher.getAuthTag()

cipher.setAutoPadding(auto_padding=true)

cipher.update(data[, input_encoding][,
output_encoding])
Class: Decipher

decipher.final([output_encoding])

decipher.setAAD(buffer)

decipher.setAuthTag(buffer)

decipher.setAutoPadding(auto_padding=true)

decipher.update(data[, input_encoding][,
output_encoding])
Class: DiffieHellman

diffieHellman.computeSecret(other_public_key[,
input_encoding][, output_encoding])

diffieHellman.generateKeys([encoding])

diffieHellman.getGenerator([encoding])

diffieHellman.getPrime([encoding])

diffieHellman.getPrivateKey([encoding])

diffieHellman.getPublicKey([encoding])

diffieHellman.setPrivateKey(private_key[, encoding])

diffieHellman.setPublicKey(public_key[, encoding])

diffieHellman.verifyError
Class: ECDH

ecdh.computeSecret(other_public_key[, input_encoding]
[, output_encoding])

ecdh.generateKeys([encoding[, format]])

ecdh.getPrivateKey([encoding])

ecdh.getPublicKey([encoding[, format]])

ecdh.setPrivateKey(private_key[, encoding])

ecdh.setPublicKey(public_key[, encoding])
Class: Hash

hash.digest([encoding])

hash.update(data[, input_encoding])
Class: Hmac

hmac.digest([encoding])

hmac.update(data[, input_encoding])
Class: Sign

sign.sign(private_key[, output_format])

sign.update(data[, input_encoding])
Class: Verify

verifier.update(data[, input_encoding])

verifier.verify(object, signature[, signature_format])

crypto module methods and properties

crypto.DEFAULT_ENCODING

crypto.fips

crypto.createCipher(algorithm, password)

crypto.createCipheriv(algorithm, key, iv)

crypto.createCredentials(details)

crypto.createDecipher(algorithm, password)

crypto.createDecipheriv(algorithm, key, iv)

crypto.createDiffieHellman(prime[, prime_encoding][,
generator][, generator_encoding])

crypto.createDiffieHellman(prime_length[, generator])

crypto.createECDH(curve_name)

crypto.createHash(algorithm)

crypto.createHmac(algorithm, key)

crypto.createSign(algorithm)

crypto.createVerify(algorithm)

crypto.getCiphers()

crypto.getCurves()

crypto.getDiffieHellman(group_name)

crypto.getHashes()

crypto.pbkdf2(password, salt, iterations, keylen, digest,

callback)

crypto.pbkdf2Sync(password, salt, iterations, keylen,

digest)

crypto.privateDecrypt(private_key, buffer)

crypto.privateEncrypt(private_key, buffer)

crypto.publicDecrypt(public_key, buffer)

crypto.publicEncrypt(public_key, buffer)

crypto.randomBytes(size[, callback])

crypto.setEngine(engine[, flags])
Notes

Legacy Streams API (pre Node.js v0.10)

Recent ECDH Changes

Support for weak or compromised algorithms

Crypto#
Stability: 2 - Stable
The crypto module provides cryptographic functionality that includes a set
of wrappers for OpenSSL's hash, HMAC, cipher, decipher, sign and verify
functions.
Use require('crypto') to access this module.
const crypto = require('crypto');
const secret = 'abcdefg';
const hash = crypto.createHmac('sha256', secret)
.update('I love cupcakes')
.digest('hex');
console.log(hash);
// Prints:
//
c0fa1bc00531bd78ef38c628449c5102aeabd49b5dc3a2a516ea6ea95
9d6658e
Determining if crypto support is unavailable#
It is possible for Node.js to be built without including support for
the crypto module. In such cases, calling require('crypto') will result in an
error being thrown.
var crypto;
try {
crypto = require('crypto');

} catch (err) {
console.log('crypto support is disabled!');
}
Class: Certificate#
SPKAC is a Certificate Signing Request mechanism originally implemented
by Netscape and now specified formally as part
of HTML5's keygen element.
The crypto module provides the Certificate class for working with SPKAC
data. The most common usage is handling output generated by the
HTML5<keygen> element. Node.js uses OpenSSL's SPKAC
implementation internally.
new crypto.Certificate()#
Instances of the Certificate class can be created using the new keyword or
by calling crypto.Certificate() as a function:
const crypto = require('crypto');
const cert1 = new crypto.Certificate();
const cert2 = crypto.Certificate();
certificate.exportChallenge(spkac)#
The spkac data structure includes a public key and a challenge.
The certificate.exportChallenge() returns the challenge component in the
form of a Node.js Buffer. The spkac argument can be either a string or
a Buffer.
const cert = require('crypto').Certificate();
const spkac = getSpkacSomehow();
const challenge = cert.exportChallenge(spkac);
console.log(challenge.toString('utf8'));
// Prints the challenge as a UTF8 string
certificate.exportPublicKey(spkac)#
The spkac data structure includes a public key and a challenge.
The certificate.exportPublicKey() returns the public key component in the

form of a Node.js Buffer. The spkac argument can be either a string or

a Buffer.
const cert = require('crypto').Certificate();
const spkac = getSpkacSomehow();
const publicKey = cert.exportPublicKey(spkac);
console.log(publicKey);
// Prints the public key as <Buffer ...>
certificate.verifySpkac(spkac)#
Returns true if the given spkac data structure is valid, false otherwise.
The spkac argument must be a Node.js Buffer.
const cert = require('crypto').Certificate();
const spkac = getSpkacSomehow();
console.log(cert.verifySpkac(Buffer.from(spkac)));
// Prints true or false
Class: Cipher#
Instances of the Cipher class are used to encrypt data. The class can be
used in one of two ways:

As a stream that is both readable and writable, where plain

unencrypted data is written to produce encrypted data on the
readable side, or

Using the cipher.update() and cipher.final() methods to produce the

encrypted data.

The crypto.createCipher() or crypto.createCipheriv() methods are used to

create Cipher instances. Cipher objects are not to be created directly
using the new keyword.
Example: Using Cipher objects as streams:
const crypto = require('crypto');
const cipher = crypto.createCipher('aes192', 'a password');
var encrypted = '';
cipher.on('readable', () => {
var data = cipher.read();

if (data)
encrypted += data.toString('hex');
});
cipher.on('end', () => {
console.log(encrypted);
// Prints:
ca981be48e90867604588e75d04feabb63cc007a8f8ad89b10616ed84
d815504
});
cipher.write('some clear text data');
cipher.end();
Example: Using Cipher and piped streams:
const crypto = require('crypto');
const fs = require('fs');
const cipher = crypto.createCipher('aes192', 'a password');
const input = fs.createReadStream('test.js');
const output = fs.createWriteStream('test.enc');
input.pipe(cipher).pipe(output);
Example: Using the cipher.update() and cipher.final() methods:
const crypto = require('crypto');
const cipher = crypto.createCipher('aes192', 'a password');
var encrypted = cipher.update('some clear text data', 'utf8', 'hex');
encrypted += cipher.final('hex');
console.log(encrypted);
// Prints:
ca981be48e90867604588e75d04feabb63cc007a8f8ad89b10616ed84
d815504

cipher.final([output_encoding])#
Returns any remaining enciphered contents. If output_encoding parameter
is one of 'binary', 'base64' or 'hex', a string is returned. If
anoutput_encoding is not provided, a Buffer is returned.
Once the cipher.final() method has been called, the Cipher object can no
longer be used to encrypt data. Attempts to call cipher.final() more than
once will result in an error being thrown.
cipher.setAAD(buffer)#
When using an authenticated encryption mode (only GCM is currently
supported), the cipher.setAAD() method sets the value used for
the additional authenticated data (AAD) input parameter.
cipher.getAuthTag()#
When using an authenticated encryption mode (only GCM is currently
supported), the cipher.getAuthTag() method returns a Buffer containing
theauthentication tag that has been computed from the given data.
The cipher.getAuthTag() method should only be called after encryption has
been completed using the cipher.final() method.
cipher.setAutoPadding(auto_padding=true)#
When using block encryption algorithms, the Cipher class will
automatically add padding to the input data to the appropriate block size.
To disable the default padding call cipher.setAutoPadding(false).
When auto_padding is false, the length of the entire input data must be a
multiple of the cipher's block size or cipher.final() will throw an Error.
Disabling automatic padding is useful for non-standard padding, for
instance using 0x0 instead of PKCS padding.
The cipher.setAutoPadding() method must be called before cipher.final().
cipher.update(data[, input_encoding][, output_encoding])#
Updates the cipher with data. If the input_encoding argument is given, it's
value must be one of 'utf8', 'ascii', or 'binary' and the dataargument is a

string using the specified encoding. If the input_encoding argument is not

given, data must be a Buffer. If data is a Buffer theninput_encoding is
ignored.
The output_encoding specifies the output format of the enciphered data,
and can be 'binary', 'base64' or 'hex'. If the output_encoding is specified, a
string using the specified encoding is returned. If no output_encoding is
provided, a Buffer is returned.
The cipher.update() method can be called multiple times with new data
until cipher.final() is called. Calling cipher.update() after cipher.final()will
result in an error being thrown.
Class: Decipher#
Instances of the Decipher class are used to decrypt data. The class can be
used in one of two ways:

As a stream that is both readable and writable, where plain

encrypted data is written to produce unencrypted data on the
readable side, or

Using the decipher.update() and decipher.final() methods to produce

the unencrypted data.

The crypto.createDecipher() or crypto.createDecipheriv() methods are

used to create Decipher instances. Decipher objects are not to be created
directly using the new keyword.
Example: Using Decipher objects as streams:
const crypto = require('crypto');
const decipher = crypto.createDecipher('aes192', 'a password');
var decrypted = '';
decipher.on('readable', () => {
var data = decipher.read();
if (data)
decrypted += data.toString('utf8');
});
decipher.on('end', () => {

console.log(decrypted);
// Prints: some clear text data
});
var encrypted =
'ca981be48e90867604588e75d04feabb63cc007a8f8ad89b10616ed84
d815504';
decipher.write(encrypted, 'hex');
decipher.end();
Example: Using Decipher and piped streams:
const crypto = require('crypto');
const fs = require('fs');
const decipher = crypto.createDecipher('aes192', 'a password');
const input = fs.createReadStream('test.enc');
const output = fs.createWriteStream('test.js');
input.pipe(decipher).pipe(output);
Example: Using the decipher.update() and decipher.final() methods:
const crypto = require('crypto');
const decipher = crypto.createDecipher('aes192', 'a password');
var encrypted =
'ca981be48e90867604588e75d04feabb63cc007a8f8ad89b10616ed84
d815504';
var decrypted = decipher.update(encrypted, 'hex', 'utf8');
decrypted += decipher.final('utf8');
console.log(decrypted);
// Prints: some clear text data
decipher.final([output_encoding])#
Returns any remaining deciphered contents. If output_encoding parameter
is one of 'binary', 'base64' or 'hex', a string is returned. If
anoutput_encoding is not provided, a Buffer is returned.

Once the decipher.final() method has been called, the Decipher object can
no longer be used to decrypt data. Attempts to call decipher.final()more
than once will result in an error being thrown.
decipher.setAAD(buffer)#
When using an authenticated encryption mode (only GCM is currently
supported), the cipher.setAAD() method sets the value used for
the additional authenticated data (AAD) input parameter.
decipher.setAuthTag(buffer)#
When using an authenticated encryption mode (only GCM is currently
supported), the decipher.setAuthTag() method is used to pass in the
receivedauthentication tag. If no tag is provided, or if the cipher text has
been tampered with, decipher.final() with throw, indicating that the cipher
text should be discarded due to failed authentication.
decipher.setAutoPadding(auto_padding=true)#
When data has been encrypted without standard block padding,
calling decipher.setAutoPadding(false) will disable automatic padding to
preventdecipher.final() from checking for and removing padding.
Turning auto padding off will only work if the input data's length is a
multiple of the ciphers block size.
The decipher.setAutoPadding() method must be called
before decipher.update().
decipher.update(data[, input_encoding][, output_encoding])#
Updates the decipher with data. If the input_encoding argument is given,
it's value must be one of 'binary', 'base64', or 'hex' and the dataargument
is a string using the specified encoding. If the input_encoding argument is
not given, data must be a Buffer. If data is a Buffer theninput_encoding is
ignored.
The output_encoding specifies the output format of the enciphered data,
and can be 'binary', 'ascii' or 'utf8'. If the output_encoding is specified, a

string using the specified encoding is returned. If no output_encoding is

provided, a Buffer is returned.
The decipher.update() method can be called multiple times with new data
until decipher.final() is called.
Calling decipher.update() afterdecipher.final() will result in an error being
thrown.
Class: DiffieHellman#
The DiffieHellman class is a utility for creating Diffie-Hellman key
exchanges.
Instances of the DiffieHellman class can be created using
the crypto.createDiffieHellman() function.
const crypto = require('crypto');
const assert = require('assert');
// Generate Alice's keys...
const alice = crypto.createDiffieHellman(2048);
const alice_key = alice.generateKeys();
// Generate Bob's keys...
const bob = crypto.createDiffieHellman(alice.getPrime(),
alice.getGenerator());
const bob_key = bob.generateKeys();
// Exchange and generate the secret...
const alice_secret = alice.computeSecret(bob_key);
const bob_secret = bob.computeSecret(alice_key);
// OK
assert.equal(alice_secret.toString('hex'), bob_secret.toString('hex'));
diffieHellman.computeSecret(other_public_key[, input_encoding][,
output_encoding])#
Computes the shared secret using other_public_key as the other party's
public key and returns the computed shared secret. The supplied key is
interpreted using the specified input_encoding, and secret is encoded

using specified output_encoding. Encodings can be 'binary', 'hex',

or'base64'. If the input_encoding is not provided, other_public_key is
expected to be a Buffer.
If output_encoding is given a string is returned; otherwise, a Buffer is
returned.
diffieHellman.generateKeys([encoding])#
Generates private and public Diffie-Hellman key values, and returns the
public key in the specified encoding. This key should be transferred to the
other party. Encoding can be 'binary', 'hex', or 'base64'. If encoding is
provided a string is returned; otherwise a Buffer is returned.
diffieHellman.getGenerator([encoding])#
Returns the Diffie-Hellman generator in the specified encoding, which can
be 'binary', 'hex', or 'base64'. If encoding is provided a string is returned;
otherwise a Buffer is returned.
diffieHellman.getPrime([encoding])#
Returns the Diffie-Hellman prime in the specified encoding, which can
be 'binary', 'hex', or 'base64'. If encoding is provided a string is returned;
otherwise a Buffer is returned.
diffieHellman.getPrivateKey([encoding])#
Returns the Diffie-Hellman private key in the specified encoding, which
can be 'binary', 'hex', or 'base64'. If encoding is provided a string is
returned; otherwise a Buffer is returned.
diffieHellman.getPublicKey([encoding])#
Returns the Diffie-Hellman public key in the specified encoding, which can
be 'binary', 'hex', or 'base64'. If encoding is provided a string is returned;
otherwise a Buffer is returned.

diffieHellman.setPrivateKey(private_key[, encoding])#
Sets the Diffie-Hellman private key. If the encoding argument is provided
and is either 'binary', 'hex', or 'base64', private_key is expected to be a
string. If no encoding is provided, private_key is expected to be a Buffer.
diffieHellman.setPublicKey(public_key[, encoding])#
Sets the Diffie-Hellman public key. If the encoding argument is provided
and is either 'binary', 'hex' or 'base64', public_key is expected to be a
string. If no encoding is provided, public_key is expected to be a Buffer.
diffieHellman.verifyError#
A bit field containing any warnings and/or errors resulting from a check
performed during initialization of the DiffieHellman object.
The following values are valid for this property (as defined
in constants module):

DH_CHECK_P_NOT_SAFE_PRIME

DH_CHECK_P_NOT_PRIME

DH_UNABLE_TO_CHECK_GENERATOR

DH_NOT_SUITABLE_GENERATOR

Class: ECDH#
The ECDH class is a utility for creating Elliptic Curve Diffie-Hellman (ECDH)
key exchanges.
Instances of the ECDH class can be created using
the crypto.createECDH() function.
const crypto = require('crypto');
const assert = require('assert');
// Generate Alice's keys...
const alice = crypto.createECDH('secp521r1');
const alice_key = alice.generateKeys();

// Generate Bob's keys...

const bob = crypto.createECDH('secp521r1');
const bob_key = bob.generateKeys();
// Exchange and generate the secret...
const alice_secret = alice.computeSecret(bob_key);
const bob_secret = bob.computeSecret(alice_key);
assert(alice_secret, bob_secret);
// OK
ecdh.computeSecret(other_public_key[, input_encoding][,
output_encoding])#
Computes the shared secret using other_public_key as the other party's
public key and returns the computed shared secret. The supplied key is
interpreted using specified input_encoding, and the returned secret is
encoded using the specified output_encoding. Encodings can
be 'binary','hex', or 'base64'. If the input_encoding is not
provided, other_public_key is expected to be a Buffer.
If output_encoding is given a string will be returned; otherwise a Buffer is
returned.
ecdh.generateKeys([encoding[, format]])#
Generates private and public EC Diffie-Hellman key values, and returns
the public key in the specified format and encoding. This key should be
transferred to the other party.
The format arguments specifies point encoding and can
be 'compressed', 'uncompressed', or 'hybrid'. If format is not specified, the
point will be returned in 'uncompressed' format.
The encoding argument can be 'binary', 'hex', or 'base64'. If encoding is
provided a string is returned; otherwise a Buffer is returned.

ecdh.getPrivateKey([encoding])#
Returns the EC Diffie-Hellman private key in the specified encoding, which
can be 'binary', 'hex', or 'base64'. If encoding is provided a string is
returned; otherwise a Buffer is returned.
ecdh.getPublicKey([encoding[, format]])#
Returns the EC Diffie-Hellman public key in the
specified encoding and format.
The format argument specifies point encoding and can
be 'compressed', 'uncompressed', or 'hybrid'. If format is not specified the
point will be returned in 'uncompressed' format.
The encoding argument can be 'binary', 'hex', or 'base64'. If encoding is
specified, a string is returned; otherwise a Buffer is returned.
ecdh.setPrivateKey(private_key[, encoding])#
Sets the EC Diffie-Hellman private key. The encoding can
be 'binary', 'hex' or 'base64'. If encoding is provided, private_key is
expected to be a string; otherwise private_key is expected to be a Buffer.
If private_key is not valid for the curve specified when the ECDH object
was created, an error is thrown. Upon setting the private key, the
associated public point (key) is also generated and set in the ECDH object.
ecdh.setPublicKey(public_key[, encoding])#
Stability: 0 - Deprecated
Sets the EC Diffie-Hellman public key. Key encoding can
be 'binary', 'hex' or 'base64'. If encoding is provided public_key is
expected to be a string; otherwise a Buffer is expected.
Note that there is not normally a reason to call this method
because ECDH only requires a private key and the other party's public key
to compute the shared secret. Typically
either ecdh.generateKeys() or ecdh.setPrivateKey() will be called.
The ecdh.setPrivateKey() method attempts to generate the public
point/key associated with the private key being set.

Example (obtaining a shared secret):

const crypto = require('crypto');
const alice = crypto.createECDH('secp256k1');
const bob = crypto.createECDH('secp256k1');
// Note: This is a shortcut way to specify one of Alice's previous private
// keys. It would be unwise to use such a predictable private key in a
real
// application.
alice.setPrivateKey(
crypto.createHash('sha256').update('alice', 'utf8').digest()
);
// Bob uses a newly generated cryptographically strong
// pseudorandom key pair bob.generateKeys();
const alice_secret = alice.computeSecret(bob.getPublicKey(), null,
'hex');
const bob_secret = bob.computeSecret(alice.getPublicKey(), null,
'hex');
// alice_secret and bob_secret should be the same shared secret value
console.log(alice_secret === bob_secret);
Class: Hash#
The Hash class is a utility for creating hash digests of data. It can be used
in one of two ways:

As a stream that is both readable and writable, where data is written

to produce a computed hash digest on the readable side, or

Using the hash.update() and hash.digest() methods to produce the

computed hash.

The crypto.createHash() method is used to

create Hash instances. Hash objects are not to be created directly using
the new keyword.
Example: Using Hash objects as streams:

const crypto = require('crypto');

const hash = crypto.createHash('sha256');
hash.on('readable', () => {
var data = hash.read();
if (data)
console.log(data.toString('hex'));
// Prints:
//
6a2da20943931e9834fc12cfe5bb47bbd9ae43489a30726962b576f4e
3993e50
});
hash.write('some data to hash');
hash.end();
Example: Using Hash and piped streams:
const crypto = require('crypto');
const fs = require('fs');
const hash = crypto.createHash('sha256');
const input = fs.createReadStream('test.js');
input.pipe(hash).pipe(process.stdout);
Example: Using the hash.update() and hash.digest() methods:
const crypto = require('crypto');
const hash = crypto.createHash('sha256');
hash.update('some data to hash');
console.log(hash.digest('hex'));
// Prints:
//
6a2da20943931e9834fc12cfe5bb47bbd9ae43489a30726962b576f4e
3993e50

hash.digest([encoding])#
Calculates the digest of all of the data passed to be hashed (using
the hash.update() method). The encoding can
be 'hex', 'binary' or 'base64'. Ifencoding is provided a string will be
returned; otherwise a Buffer is returned.
The Hash object can not be used again after hash.digest() method has
been called. Multiple calls will cause an error to be thrown.
hash.update(data[, input_encoding])#
Updates the hash content with the given data, the encoding of which is
given in input_encoding and can be 'utf8', 'ascii' or 'binary'. If encodingis
not provided, and the data is a string, an encoding of 'utf8' is enforced.
If data is a Buffer then input_encoding is ignored.
This can be called many times with new data as it is streamed.
Class: Hmac#
The Hmac Class is a utility for creating cryptographic HMAC digests. It can
be used in one of two ways:

As a stream that is both readable and writable, where data is written

to produce a computed HMAC digest on the readable side, or

Using the hmac.update() and hmac.digest() methods to produce the

computed HMAC digest.

The crypto.createHmac() method is used to

create Hmac instances. Hmac objects are not to be created directly using
the new keyword.
Example: Using Hmac objects as streams:
const crypto = require('crypto');
const hmac = crypto.createHmac('sha256', 'a secret');
hmac.on('readable', () => {
var data = hmac.read();
if (data)

console.log(data.toString('hex'));
// Prints:
//
7fd04df92f636fd450bc841c9418e5825c17f33ad9c87c518115a45971f
7f77e
});
hmac.write('some data to hash');
hmac.end();
Example: Using Hmac and piped streams:
const crypto = require('crypto');
const fs = require('fs');
const hmac = crypto.createHmac('sha256', 'a secret');
const input = fs.createReadStream('test.js');
input.pipe(hmac).pipe(process.stdout);
Example: Using the hmac.update() and hmac.digest() methods:
const crypto = require('crypto');
const hmac = crypto.createHmac('sha256', 'a secret');
hmac.update('some data to hash');
console.log(hmac.digest('hex'));
// Prints:
//
7fd04df92f636fd450bc841c9418e5825c17f33ad9c87c518115a45971f
7f77e
hmac.digest([encoding])#
Calculates the HMAC digest of all of the data passed using hmac.update().
The encoding can be 'hex', 'binary' or 'base64'. If encoding is provided a
string is returned; otherwise a Buffer is returned;
The Hmac object can not be used again after hmac.digest() has been
called. Multiple calls to hmac.digest() will result in an error being thrown.

hmac.update(data[, input_encoding])#
Updates the Hmac content with the given data, the encoding of which is
given in input_encoding and can be 'utf8', 'ascii' or 'binary'. Ifencoding is
not provided, and the data is a string, an encoding of 'utf8' is enforced.
If data is a Buffer then input_encoding is ignored.
This can be called many times with new data as it is streamed.
Class: Sign#
The Sign Class is a utility for generating signatures. It can be used in one
of two ways:

As a writable stream, where data to be signed is written and

the sign.sign() method is used to generate and return the signature, or

Using the sign.update() and sign.sign() methods to produce the

signature.

The crypto.createSign() method is used to

create Sign instances. Sign objects are not to be created directly using
the new keyword.
Example: Using Sign objects as streams:
const crypto = require('crypto');
const sign = crypto.createSign('RSA-SHA256');
sign.write('some data to sign');
sign.end();
const private_key = getPrivateKeySomehow();
console.log(sign.sign(private_key, 'hex'));
// Prints the calculated signature
Example: Using the sign.update() and sign.sign() methods:
const crypto = require('crypto');
const sign = crypto.createSign('RSA-SHA256');
sign.update('some data to sign');

const private_key = getPrivateKeySomehow();

console.log(sign.sign(private_key, 'hex'));
// Prints the calculated signature
A [sign][] instance can also be created by just passing in the digest
algorithm name, in which case OpenSSL will infer the full signature
algorithm from the type of the PEM-formatted private key, including
algorithms that do not have directly exposed name constants, e.g. 'ecdsawith-SHA256'.
Example: signing using ECDSA with SHA256
const crypto = require('crypto');
const sign = crypto.createSign('sha256');
sign.update('some data to sign');
const private_key = '-----BEGIN EC PRIVATE KEY-----\n' +
'MHcCAQEEIF+jnWY1D5kbVYDNvxxo/Y+ku2uJPDwS0r/VuPZQrjjVoAoGC
CqGSM49\n' +
'AwEHoUQDQgAEurOxfSxmqIRYzJVagdZfMMSjRNNhB8i3mXyIMq704m2
m52FdfKZ2\n' +
'pQhByd5eyj3lgZ7m7jbchtdgyOF8Io/1ng==\n' +
'-----END EC PRIVATE KEY-----\n';
console.log(sign.sign(private_key).toString('hex'));
sign.sign(private_key[, output_format])#
Calculates the signature on all the data passed through using
either sign.update() or sign.write().
The private_key argument can be an object or a string. If private_key is a
string, it is treated as a raw key with no passphrase. If private_key is an
object, it is interpreted as a hash containing two properties:

key : <String> - PEM encoded private key

passphrase : <String> - passphrase for the private key

The output_format can specify one of 'binary', 'hex' or 'base64'.

If output_format is provided a string is returned; otherwise a Buffer is
returned.
The Sign object can not be again used after sign.sign() method has been
called. Multiple calls to sign.sign() will result in an error being thrown.
sign.update(data[, input_encoding])#
Updates the Sign content with the given data, the encoding of which is
given in input_encoding and can be 'utf8', 'ascii' or 'binary'. Ifencoding is
not provided, and the data is a string, an encoding of 'utf8' is enforced.
If data is a Buffer then input_encoding is ignored.
This can be called many times with new data as it is streamed.
Class: Verify#
The Verify class is a utility for verifying signatures. It can be used in one of
two ways:

As a writable stream where written data is used to validate against

the supplied signature, or

Using the verify.update() and verify.verify() methods to verify the

signature.
The crypto.createSign() method is used to
create Sign instances. Sign objects are not to be created directly using
the new keyword.

Example: Using Verify objects as streams:

const crypto = require('crypto');
const verify = crypto.createVerify('RSA-SHA256');
verify.write('some data to sign');
verify.end();
const public_key = getPublicKeySomehow();

const signature = getSignatureToVerify();

console.log(sign.verify(public_key, signature));
// Prints true or false
Example: Using the verify.update() and verify.verify() methods:
const crypto = require('crypto');
const verify = crypto.createVerify('RSA-SHA256');
verify.update('some data to sign');
const public_key = getPublicKeySomehow();
const signature = getSignatureToVerify();
console.log(verify.verify(public_key, signature));
// Prints true or false
verifier.update(data[, input_encoding])#
Updates the Verify content with the given data, the encoding of which is
given in input_encoding and can be 'utf8', 'ascii' or 'binary'. Ifencoding is
not provided, and the data is a string, an encoding of 'utf8' is enforced.
If data is a Buffer then input_encoding is ignored.
This can be called many times with new data as it is streamed.
verifier.verify(object, signature[, signature_format])#
Verifies the provided data using the given object and signature.
The object argument is a string containing a PEM encoded object, which
can be one an RSA public key, a DSA public key, or an X.509 certificate.
The signature argument is the previously calculated signature for the
data, in thesignature_format which can be 'binary', 'hex' or 'base64'. If
a signature_format is specified, the signature is expected to be a string;
otherwisesignature is expected to be a Buffer.
Returns true or false depending on the validity of the signature for the
data and public key.
The verifier object can not be used again after verify.verify() has been
called. Multiple calls to verify.verify() will result in an error being thrown.
crypto module methods and properties#

crypto.DEFAULT_ENCODING#
The default encoding to use for functions that can take either strings
or buffers. The default value is 'buffer', which makes methods default
to Bufferobjects.
The crypto.DEFAULT_ENCODING mechanism is provided for backwards
compatibility with legacy programs that expect 'binary' to be the default
encoding.
New applications should expect the default to be 'buffer'. This property
may become deprecated in a future Node.js release.
crypto.fips#
Property for checking and controlling whether a FIPS compliant crypto
provider is currently in use. Setting to true requires a FIPS build of Node.js.
crypto.createCipher(algorithm, password)#
Creates and returns a Cipher object that uses the
given algorithm and password.
The algorithm is dependent on OpenSSL, examples are 'aes192', etc. On
recent OpenSSL releases, openssl list-cipher-algorithms will display the
available cipher algorithms.
The password is used to derive the cipher key and initialization vector (IV).
The value must be either a 'binary' encoded string or a Buffer.
The implementation of crypto.createCipher() derives keys using the
OpenSSL function EVP_BytesToKey with the digest algorithm set to MD5,
one iteration, and no salt. The lack of salt allows dictionary attacks as the
same password always creates the same key. The low iteration count and
non-cryptographically secure hash algorithm allow passwords to be tested
very rapidly.
In line with OpenSSL's recommendation to use pbkdf2 instead
of EVP_BytesToKey it is recommended that developers derive a key and IV
on their own using crypto.pbkdf2() and to use crypto.createCipheriv() to
create the Cipher object.

crypto.createCipheriv(algorithm, key, iv)#

Creates and returns a Cipher object, with the given algorithm, key and
initialization vector (iv).
The algorithm is dependent on OpenSSL, examples are 'aes192', etc. On
recent OpenSSL releases, openssl list-cipher-algorithms will display the
available cipher algorithms.
The key is the raw key used by the algorithm and iv is an initialization
vector. Both arguments must be 'binary' encoded strings or buffers.
crypto.createCredentials(details)#
Stability: 0 - Deprecated: Use tls.createSecureContext() instead.
The crypto.createCredentials() method is a deprecated alias for creating
and returning a tls.SecureContext object.
Thecrypto.createCredentials() method should not be used.
The optional details argument is a hash object with keys:

pfx : <String> | <Buffer> - PFX or PKCS12 encoded private key,

certificate and CA certificates

key : <String> - PEM encoded private key

passphrase : <String> - passphrase for the private key or PFX

cert : <String> - PEM encoded certificate

ca : <String> | <Array> - Either a string or array of strings of PEM

encoded CA certificates to trust.

crl : <String> | <Array> - Either a string or array of strings of PEM

encoded CRLs (Certificate Revocation List)

ciphers: <String> using the OpenSSL cipher list format describing

the cipher algorithms to use or exclude.

If no 'ca' details are given, Node.js will use Mozilla's default publicly
trusted list of CAs.

crypto.createDecipher(algorithm, password)#
Creates and returns a Decipher object that uses the
given algorithm and password (key).
The implementation of crypto.createDecipher() derives keys using the
OpenSSL function EVP_BytesToKey with the digest algorithm set to MD5,
one iteration, and no salt. The lack of salt allows dictionary attacks as the
same password always creates the same key. The low iteration count and
non-cryptographically secure hash algorithm allow passwords to be tested
very rapidly.
In line with OpenSSL's recommendation to use pbkdf2 instead
of EVP_BytesToKey it is recommended that developers derive a key and IV
on their own using crypto.pbkdf2() and to use crypto.createDecipheriv() to
create the Decipher object.
crypto.createDecipheriv(algorithm, key, iv)#
Creates and returns a Decipher object that uses the
given algorithm, key and initialization vector (iv).
The algorithm is dependent on OpenSSL, examples are 'aes192', etc. On
recent OpenSSL releases, openssl list-cipher-algorithms will display the
available cipher algorithms.
The key is the raw key used by the algorithm and iv is an initialization
vector. Both arguments must be 'binary' encoded strings or buffers.
crypto.createDiffieHellman(prime[, prime_encoding][, generator][,
generator_encoding])#
Creates a DiffieHellman key exchange object using the supplied prime and
an optional specific generator.
The generator argument can be a number, string, or Buffer. If generator is
not specified, the value 2 is used.
The prime_encoding and generator_encoding arguments can
be 'binary', 'hex', or 'base64'.

If prime_encoding is specified, prime is expected to be a string; otherwise

a Buffer is expected.
If generator_encoding is specified, generator is expected to be a string;
otherwise either a number or Buffer is expected.
crypto.createDiffieHellman(prime_length[, generator])#
Creates a DiffieHellman key exchange object and generates a prime
of prime_length bits using an optional specific numeric generator.
If generator is not specified, the value 2 is used.
crypto.createECDH(curve_name)#
Creates an Elliptic Curve Diffie-Hellman (ECDH) key exchange object using
a predefined curve specified by the curve_name string.
Usecrypto.getCurves() to obtain a list of available curve names. On recent
OpenSSL releases, openssl ecparam -list_curves will also display the name
and description of each available elliptic curve.
crypto.createHash(algorithm)#
Creates and returns a Hash object that can be used to generate hash
digests using the given algorithm.
The algorithm is dependent on the available algorithms supported by the
version of OpenSSL on the platform. Examples are 'sha256', 'sha512', etc.
On recent releases of OpenSSL, openssl list-message-digestalgorithms will display the available digest algorithms.
Example: generating the sha256 sum of a file
const filename = process.argv[2];
const crypto = require('crypto');
const fs = require('fs');
const hash = crypto.createHash('sha256');
const input = fs.createReadStream(filename);
input.on('readable', () => {
var data = input.read();

if (data)
hash.update(data);
else {
console.log(`${hash.digest('hex')} ${filename}`);
}
});
crypto.createHmac(algorithm, key)#
Creates and returns an Hmac object that uses the
given algorithm and key.
The algorithm is dependent on the available algorithms supported by the
version of OpenSSL on the platform. Examples are 'sha256', 'sha512', etc.
On recent releases of OpenSSL, openssl list-message-digestalgorithms will display the available digest algorithms.
The key is the HMAC key used to generate the cryptographic HMAC hash.
Example: generating the sha256 HMAC of a file
const filename = process.argv[2];
const crypto = require('crypto');
const fs = require('fs');
const hmac = crypto.createHmac('sha256', 'a secret');
const input = fs.createReadStream(filename);
input.on('readable', () => {
var data = input.read();
if (data)
hmac.update(data);
else {
console.log(`${hmac.digest('hex')} ${filename}`);
}
});
crypto.createSign(algorithm)#
Creates and returns a Sign object that uses the given algorithm. On recent
OpenSSL releases, openssl list-public-key-algorithms will display the
available signing algorithms. One example is 'RSA-SHA256'.

crypto.createVerify(algorithm)#
Creates and returns a Verify object that uses the given algorithm. On
recent OpenSSL releases, openssl list-public-key-algorithms will display
the available signing algorithms. One example is 'RSA-SHA256'.
crypto.getCiphers()#
Returns an array with the names of the supported cipher algorithms.
Example:
const ciphers = crypto.getCiphers();
console.log(ciphers); // ['aes-128-cbc', 'aes-128-ccm', ...]
crypto.getCurves()#
Returns an array with the names of the supported elliptic curves.
Example:
const curves = crypto.getCurves();
console.log(curves); // ['secp256k1', 'secp384r1', ...]
crypto.getDiffieHellman(group_name)#
Creates a predefined DiffieHellman key exchange object. The supported
groups are: 'modp1', 'modp2', 'modp5' (defined in RFC 2412, but
seeCaveats)
and 'modp14', 'modp15', 'modp16', 'modp17', 'modp18' (defined in RFC
3526). The returned object mimics the interface of objects created
by crypto.createDiffieHellman(), but will not allow changing the keys
(with diffieHellman.setPublicKey() for example). The advantage of using
this method is that the parties do not have to generate nor exchange a
group modulus beforehand, saving both processor and communication
time.
Example (obtaining a shared secret):
const crypto = require('crypto');
const alice = crypto.getDiffieHellman('modp14');
const bob = crypto.getDiffieHellman('modp14');

alice.generateKeys();
bob.generateKeys();
const alice_secret = alice.computeSecret(bob.getPublicKey(), null,
'hex');
const bob_secret = bob.computeSecret(alice.getPublicKey(), null,
'hex');
/* alice_secret and bob_secret should be the same */
console.log(alice_secret == bob_secret);
crypto.getHashes()#
Returns an array with the names of the supported hash algorithms.
Example:
const hashes = crypto.getHashes();
console.log(hashes); // ['sha', 'sha1', 'sha1WithRSAEncryption', ...]
crypto.pbkdf2(password, salt, iterations, keylen, digest,
callback)#
Provides an asynchronous Password-Based Key Derivation Function 2
(PBKDF2) implementation. A selected HMAC digest algorithm specified
by digestis applied to derive a key of the requested byte length (keylen)
from the password, salt and iterations.
The supplied callback function is called with two
arguments: err and derivedKey. If an error occurs, err will be set;
otherwise err will be null. The successfully generated derivedKey will be
passed as a Buffer.
The iterations argument must be a number set as high as possible. The
higher the number of iterations, the more secure the derived key will be,
but will take a longer amount of time to complete.
The salt should also be as unique as possible. It is recommended that the
salts are random and their lengths are greater than 16 bytes. See NIST SP
800-132 for details.
Example:

const crypto = require('crypto');

crypto.pbkdf2('secret', 'salt', 100000, 512, 'sha512', (err, key) => {
if (err) throw err;
console.log(key.toString('hex')); // 'c5e478d...1469e50'
});
An array of supported digest functions can be retrieved
using crypto.getHashes().
crypto.pbkdf2Sync(password, salt, iterations, keylen, digest)#
Provides a synchronous Password-Based Key Derivation Function 2
(PBKDF2) implementation. A selected HMAC digest algorithm specified
by digest is applied to derive a key of the requested byte length (keylen)
from the password, salt and iterations.
If an error occurs an Error will be thrown, otherwise the derived key will be
returned as a Buffer.
The iterations argument must be a number set as high as possible. The
higher the number of iterations, the more secure the derived key will be,
but will take a longer amount of time to complete.
The salt should also be as unique as possible. It is recommended that the
salts are random and their lengths are greater than 16 bytes. See NIST SP
800-132 for details.
Example:
const crypto = require('crypto');
const key = crypto.pbkdf2Sync('secret', 'salt', 100000, 512, 'sha512');
console.log(key.toString('hex')); // 'c5e478d...1469e50'
An array of supported digest functions can be retrieved
using crypto.getHashes().
crypto.privateDecrypt(private_key, buffer)#
Decrypts buffer with private_key.

private_key can be an object or a string. If private_key is a string, it is

treated as the key with no passphrase and will
use RSA_PKCS1_OAEP_PADDING. Ifprivate_key is an object, it is interpreted
as a hash object with the keys:

key : <String> - PEM encoded private key

passphrase : <String> - Optional passphrase for the private key

padding : An optional padding value, one of the following:

o

constants.RSA_NO_PADDING

constants.RSA_PKCS1_PADDING

constants.RSA_PKCS1_OAEP_PADDING

All paddings are defined in the constants module.

crypto.privateEncrypt(private_key, buffer)#
Encrypts buffer with private_key.
private_key can be an object or a string. If private_key is a string, it is
treated as the key with no passphrase and will use RSA_PKCS1_PADDING.
Ifprivate_key is an object, it is interpreted as a hash object with the keys:

key : <String> - PEM encoded private key

passphrase : <String> - Optional passphrase for the private key

padding : An optional padding value, one of the following:

o

constants.RSA_NO_PADDING

constants.RSA_PKCS1_PADDING

constants.RSA_PKCS1_OAEP_PADDING

All paddings are defined in the constants module.

crypto.publicDecrypt(public_key, buffer)#
Decrypts buffer with public_key.

public_key can be an object or a string. If public_key is a string, it is

treated as the key with no passphrase and will use RSA_PKCS1_PADDING.
Ifpublic_key is an object, it is interpreted as a hash object with the keys:

key : <String> - PEM encoded public key

passphrase : <String> - Optional passphrase for the private key

padding : An optional padding value, one of the following:

o

constants.RSA_NO_PADDING

constants.RSA_PKCS1_PADDING

constants.RSA_PKCS1_OAEP_PADDING

Because RSA public keys can be derived from private keys, a private key
may be passed instead of a public key.
All paddings are defined in the constants module.
crypto.publicEncrypt(public_key, buffer)#
Encrypts buffer with public_key.
public_key can be an object or a string. If public_key is a string, it is
treated as the key with no passphrase and will
use RSA_PKCS1_OAEP_PADDING. Ifpublic_key is an object, it is interpreted
as a hash object with the keys:

key : <String> - PEM encoded public key

passphrase : <String> - Optional passphrase for the private key

padding : An optional padding value, one of the following:

o

constants.RSA_NO_PADDING

constants.RSA_PKCS1_PADDING

constants.RSA_PKCS1_OAEP_PADDING

Because RSA public keys can be derived from private keys, a private key
may be passed instead of a public key.

All paddings are defined in the constants module.

crypto.randomBytes(size[, callback])#
Generates cryptographically strong pseudo-random data.
The size argument is a number indicating the number of bytes to
generate.
If a callback function is provided, the bytes are generated asynchronously
and the callback function is invoked with two arguments: err and buf. If an
error occurs, err will be an Error object; otherwise it is null.
The buf argument is a Buffer containing the generated bytes.
// Asynchronous
const crypto = require('crypto');
crypto.randomBytes(256, (err, buf) => {
if (err) throw err;
console.log(`${buf.length} bytes of random data: $
{buf.toString('hex')}`);
});
If the callback function is not provided, the random bytes are generated
synchronously and returned as a Buffer. An error will be thrown if there is
a problem generating the bytes.
// Synchronous
const buf = crypto.randomBytes(256);
console.log(
`${buf.length} bytes of random data: ${buf.toString('hex')}`);
The crypto.randomBytes() method will block until there is sufficient
entropy. This should normally never take longer than a few milliseconds.
The only time when generating the random bytes may conceivably block
for a longer period of time is right after boot, when the whole system is
still low on entropy.
crypto.setEngine(engine[, flags])#
Load and set the engine for some or all OpenSSL functions (selected by
flags).

engine could be either an id or a path to the engine's shared library.

The optional flags argument uses ENGINE_METHOD_ALL by default.
The flags is a bit field taking one of or a mix of the following flags (defined
in theconstants module):

ENGINE_METHOD_RSA

ENGINE_METHOD_DSA

ENGINE_METHOD_DH

ENGINE_METHOD_RAND

ENGINE_METHOD_ECDH

ENGINE_METHOD_ECDSA

ENGINE_METHOD_CIPHERS

ENGINE_METHOD_DIGESTS

ENGINE_METHOD_STORE

ENGINE_METHOD_PKEY_METHS

ENGINE_METHOD_PKEY_ASN1_METHS

ENGINE_METHOD_ALL

ENGINE_METHOD_NONE

Notes#
Legacy Streams API (pre Node.js v0.10)#
The Crypto module was added to Node.js before there was the concept of
a unified Stream API, and before there were Buffer objects for handling
binary data. As such, the many of the crypto defined classes have
methods not typically found on other Node.js classes that implement
the streams API (e.g.update(), final(), or digest()). Also, many methods
accepted and returned 'binary' encoded strings by default rather than
Buffers. This default was changed after Node.js v0.8 to use Buffer objects
by default instead.

Recent ECDH Changes#

Usage of ECDH with non-dynamically generated key pairs has been
simplified. Now, ecdh.setPrivateKey() can be called with a preselected
private key and the associated public point (key) will be computed and
stored in the object. This allows code to only store and provide the private
part of the EC key pair. ecdh.setPrivateKey() now also validates that the
private key is valid for the selected curve.
The ecdh.setPublicKey() method is now deprecated as its inclusion in the
API is not useful. Either a previously stored private key should be set,
which automatically generates the associated public key,
or ecdh.generateKeys() should be called. The main drawback of
using ecdh.setPublicKey() is that it can be used to put the ECDH key pair
into an inconsistent state.
Support for weak or compromised algorithms#
The crypto module still supports some algorithms which are already
compromised and are not currently recommended for use. The API also
allows the use of ciphers and hashes with a small key size that are
considered to be too weak for safe use.
Users should take full responsibility for selecting the crypto algorithm and
key size according to their security requirements.
Based on the recommendations of NIST SP 800-131A:

MD5 and SHA-1 are no longer acceptable where collision resistance

is required such as digital signatures.

The key used with RSA, DSA and DH algorithms is recommended to

have at least 2048 bits and that of the curve of ECDSA and ECDH at
least 224 bits, to be safe to use for several years.

The DH groups of modp1, modp2 and modp5 have a key size

smaller than 2048 bits and are not recommended.

See the reference for other recommendations and details.

Debugger

Watchers

Commands reference

Stepping

Breakpoints

Info

Execution control

Various

Advanced Usage
Debugger#
Stability: 2 - Stable
Node.js includes a full-featured out-of-process debugging utility accessible
via a simple TCP-based protocol and built-in debugging client. To use it,
start Node.js with the debug argument followed by the path to the script
to debug; a prompt will be displayed indicating successful launch of the
debugger:
$ node debug myscript.js
< debugger listening on port 5858
connecting... ok
break in /home/indutny/Code/git/indutny/myscript.js:1
1 x = 5;
2 setTimeout(() => {
3 debugger;
debug>
Node.js's debugger client does not yet support the full range of
commands, but simple step and inspection are possible.
Inserting the statement debugger; into the source code of a script will
enable a breakpoint at that position in the code.
For example, suppose myscript.js is written as:
// myscript.js

x = 5;
setTimeout(() => {
debugger;
console.log('world');
}, 1000);
console.log('hello');
Once the debugger is run, a breakpoint will occur at line 4:
$ node debug myscript.js
< debugger listening on port 5858
connecting... ok
break in /home/indutny/Code/git/indutny/myscript.js:1
1 x = 5;
2 setTimeout(() => {
3 debugger;
debug> cont
< hello
break in /home/indutny/Code/git/indutny/myscript.js:3
1 x = 5;
2 setTimeout(() => {
3 debugger;
4 console.log('world');
5 }, 1000);
debug> next
break in /home/indutny/Code/git/indutny/myscript.js:4
2 setTimeout(() => {
3 debugger;
4 console.log('world');
5 }, 1000);
6 console.log('hello');
debug> repl
Press Ctrl + C to leave debug repl
>x
5
> 2+2
4
debug> next
< world

break in /home/indutny/Code/git/indutny/myscript.js:5
3 debugger;
4 console.log('world');
5 }, 1000);
6 console.log('hello');
7
debug> quit
The repl command allows code to be evaluated remotely.
The next command steps over to the next line. Type help to see what
other commands are available.
Pressing enter without typing a command will repeat the previous
debugger command.
Watchers#
It is possible to watch expression and variable values while debugging. On
every breakpoint, each expression from the watchers list will be evaluated
in the current context and displayed immediately before the breakpoint's
source code listing.
To begin watching an expression, type watch('my_expression'). The
command watchers will print the active watchers. To remove a watcher,
typeunwatch('my_expression').
Commands reference#
Stepping#

cont, c - Continue execution

next, n - Step next

step, s - Step in

out, o - Step out

pause - Pause running code (like pause button in Developer Tools)

Breakpoints#

setBreakpoint(), sb() - Set breakpoint on current line

setBreakpoint(line), sb(line) - Set breakpoint on specific line

setBreakpoint('fn()'), sb(...) - Set breakpoint on a first statement in

functions body

setBreakpoint('script.js', 1), sb(...) - Set breakpoint on first line of

script.js

clearBreakpoint('script.js', 1), cb(...) - Clear breakpoint in script.js on

line 1

It is also possible to set a breakpoint in a file (module) that isn't loaded

yet:
$ ./node debug test/fixtures/break-in-module/main.js
< debugger listening on port 5858
connecting to port 5858... ok
break in test/fixtures/break-in-module/main.js:1
1 var mod = require('./mod.js');
2 mod.hello();
3 mod.hello();
debug> setBreakpoint('mod.js', 23)
Warning: script 'mod.js' was not loaded yet.
1 var mod = require('./mod.js');
2 mod.hello();
3 mod.hello();
debug> c
break in test/fixtures/break-in-module/mod.js:23
21
22 exports.hello = () => {
23 return 'hello from module';
24 };
25
debug>
Info#

backtrace, bt - Print backtrace of current execution frame

list(5) - List scripts source code with 5 line context (5 lines before
and after)
watch(expr) - Add expression to watch list

unwatch(expr) - Remove expression from watch list

watchers - List all watchers and their values (automatically listed on

each breakpoint)

repl - Open debugger's repl for evaluation in debugging script's

context

exec expr - Execute an expression in debugging script's context

Execution control#

run - Run script (automatically runs on debugger's start)

restart - Restart script

kill - Kill script

Various#

scripts - List all loaded scripts

version - Display V8's version

Advanced Usage#
An alternative way of enabling and accessing the debugger is to start
Node.js with the --debug command-line flag or by signaling an existing
Node.js process with SIGUSR1.
Once a process has been set in debug mode this way, it can be connected
to using the Node.js debugger by either connecting to the pid of the
running process or via URI reference to the listening debugger:

node debug -p <pid> - Connects to the process via the pid

node debug <URI> - Connects to the process via the URI such as
localhost:5858
DNS#
Stability: 2 - Stable
The dns module contains functions belonging to two different categories:
1) Functions that use the underlying operating system facilities to perform
name resolution, and that do not necessarily perform any network

communication. This category contains only one

function: dns.lookup(). Developers looking to perform name
resolution in the same way that other applications on the same
operating system behave should use dns.lookup().
For example, looking up nodejs.org.
const dns = require('dns');
dns.lookup('nodejs.org', (err, addresses, family) => {
console.log('addresses:', addresses);
});
2) Functions that connect to an actual DNS server to perform name
resolution, and that always use the network to perform DNS queries. This
category contains all functions in the dns module except dns.lookup().
These functions do not use the same set of configuration files used
by dns.lookup() (e.g./etc/hosts). These functions should be used by
developers who do not want to use the underlying operating system's
facilities for name resolution, and instead want to always perform DNS
queries.
Below is an example that resolves 'nodejs.org' then reverse resolves the IP
addresses that are returned.
const dns = require('dns');
dns.resolve4('nodejs.org', (err, addresses) => {
if (err) throw err;
console.log(`addresses: ${JSON.stringify(addresses)}`);
addresses.forEach((a) => {
dns.reverse(a, (err, hostnames) => {
if (err) {
throw err;
}
console.log(`reverse for ${a}: ${JSON.stringify(hostnames)}`);
});

});
});
There are subtle consequences in choosing one over the other, please
consult the Implementation considerations section for more information.
dns.getServers()#
Returns an array of IP address strings that are being used for name
resolution.
dns.lookup(hostname[, options], callback)#
Resolves a hostname (e.g. 'nodejs.org') into the first found A (IPv4) or
AAAA (IPv6) record. options can be an object or integer. If options is not
provided, then IPv4 and IPv6 addresses are both valid. If options is an
integer, then it must be 4 or 6.
Alternatively, options can be an object containing these properties:

family <Number> - The record family. If present, must be the

integer 4 or 6. If not provided, both IP v4 and v6 addresses are
accepted.

hints: <Number> - If present, it should be one or more of the

supported getaddrinfo flags. If hints is not provided, then no flags are
passed togetaddrinfo. Multiple flags can be passed through hints by
logically ORing their values. See supported getaddrinfo flags for more
information on supported flags.

all: <Boolean> - When true, the callback returns all resolved

addresses in an array, otherwise returns a single address. Defaults
to false.

All properties are optional. An example usage of options is shown below.

{
family: 4,
hints: dns.ADDRCONFIG | dns.V4MAPPED,
all: false
}

The callback function has arguments (err, address, family). address is a

string representation of an IPv4 or IPv6 address. family is either the
integer 4 or 6 and denotes the family of address (not necessarily the value
initially passed to lookup).
With the all option set to true, the arguments change to (err, addresses),
with addresses being an array of objects with the
properties addressand family.
On error, err is an Error object, where err.code is the error code. Keep in
mind that err.code will be set to 'ENOENT' not only when the hostname
does not exist but also when the lookup fails in other ways such as no
available file descriptors.
dns.lookup() does not necessarily have anything to do with the DNS
protocol. The implementation uses an operating system facility that can
associate names with addresses, and vice versa. This implementation can
have subtle but important consequences on the behavior of any Node.js
program. Please take some time to consult the Implementation
considerations section before using dns.lookup().
Supported getaddrinfo flags#
The following flags can be passed as hints to dns.lookup().

dns.ADDRCONFIG: Returned address types are determined by the

types of addresses supported by the current system. For example,
IPv4 addresses are only returned if the current system has at least one
IPv4 address configured. Loopback addresses are not considered.

dns.V4MAPPED: If the IPv6 family was specified, but no IPv6

addresses were found, then return IPv4 mapped IPv6 addresses. Note
that it is not supported on some operating systems (e.g FreeBSD
10.1).

dns.lookupService(address, port, callback)#

Resolves the given address and port into a hostname and service using
the operating system's underlying getnameinfo implementation.
If address is not a valid IP address, a TypeError will be thrown. The port will
be coerced to a number. If it is not a legal port, a TypeError will be thrown.

The callback has arguments (err, hostname, service).

The hostname and service arguments are strings
(e.g. 'localhost' and 'http' respectively).
On error, err is an Error object, where err.code is the error code.
const dns = require('dns');
dns.lookupService('127.0.0.1', 22, (err, hostname, service) => {
console.log(hostname, service);
// Prints: localhost ssh
});
dns.resolve(hostname[, rrtype], callback)#
Uses the DNS protocol to resolve a hostname (e.g. 'nodejs.org') into an
array of the record types specified by rrtype.
Valid values for rrtype are:

'A' - IPV4 addresses, default

'AAAA' - IPV6 addresses

'MX' - mail exchange records

'TXT' - text records

'SRV' - SRV records

'PTR' - PTR records

'NS' - name server records

'CNAME' - canonical name records

'SOA' - start of authority record

The callback function has arguments (err, addresses). When

successful, addresses will be an array. The type of each item
in addresses is determined by the record type, and described in the
documentation for the corresponding lookup methods.

On error, err is an Error object, where err.code is one of the error codes
listed here.
dns.resolve4(hostname, callback)#
Uses the DNS protocol to resolve a IPv4 addresses (A records) for
the hostname. The addresses argument passed to the callback function
will contain an array of IPv4 addresses (e.g. ['74.125.79.104',
'74.125.79.105', '74.125.79.106']).
dns.resolve6(hostname, callback)#
Uses the DNS protocol to resolve a IPv6 addresses (AAAA records) for
the hostname. The addresses argument passed to the callback function
will contain an array of IPv6 addresses.
dns.resolveCname(hostname, callback)#
Uses the DNS protocol to resolve CNAME records for the hostname.
The addresses argument passed to the callback function will contain an
array of canonical name records available for
the hostname (e.g. ['bar.example.com']).
dns.resolveMx(hostname, callback)#
Uses the DNS protocol to resolve mail exchange records (MX records) for
the hostname. The addresses argument passed to the callback function
will contain an array of objects containing both
a priority and exchange property (e.g. [{priority: 10, exchange:
'mx.example.com'}, ...]).
dns.resolveNs(hostname, callback)#
Uses the DNS protocol to resolve name server records (NS records) for
the hostname. The addresses argument passed to the callback function
will contain an array of name server records available
for hostname (e.g., ['ns1.example.com', 'ns2.example.com']).
dns.resolveSoa(hostname, callback)#

Uses the DNS protocol to resolve a start of authority record (SOA record)
for the hostname. The addresses argument passed to
the callback function will be an object with the following properties:

nsname

hostmaster

serial

refresh

retry

expire

minttl
{
nsname: 'ns.example.com',
hostmaster: 'root.example.com',
serial: 2013101809,
refresh: 10000,
retry: 2400,
expire: 604800,
minttl: 3600
}

dns.resolveSrv(hostname, callback)#
Uses the DNS protocol to resolve service records (SRV records) for
the hostname. The addresses argument passed to the callback function
will be an array of objects with the following properties:

priority

weight

port

name
{
priority: 10,
weight: 5,

port: 21223,
name: 'service.example.com'
}
dns.resolvePtr(hostname, callback)#
Uses the DNS protocol to resolve pointer records (PTR records) for
the hostname. The addresses argument passed to the callback function
will be an array of strings containing the reply records.
dns.resolveTxt(hostname, callback)#
Uses the DNS protocol to resolve text queries (TXT records) for
the hostname. The addresses argument passed to the callback function is
is a two-dimentional array of the text records available
for hostname (e.g., [ ['v=spf1 ip4:0.0.0.0 ', '~all' ] ]). Each sub-array
contains TXT chunks of one record. Depending on the use case, these
could be either joined together or treated separately.
dns.reverse(ip, callback)#
Performs a reverse DNS query that resolves an IPv4 or IPv6 address to an
array of hostnames.
The callback function has arguments (err, hostnames),
where hostnames is an array of resolved hostnames for the given ip.
On error, err is an Error object, where err.code is one of the DNS error
codes.
dns.setServers(servers)#
Sets the IP addresses of the servers to be used when resolving.
The servers argument is an array of IPv4 or IPv6 addresses.
If a port specified on the address it will be removed.
An error will be thrown if an invalid address is provided.
The dns.setServers() method must not be called while a DNS query is in
progress.

Error codes#
Each DNS query can return one of the following error codes:

dns.NODATA: DNS server returned answer with no data.

dns.FORMERR: DNS server claims query was misformatted.

dns.SERVFAIL: DNS server returned general failure.

dns.NOTFOUND: Domain name not found.

dns.NOTIMP: DNS server does not implement requested operation.

dns.REFUSED: DNS server refused query.

dns.BADQUERY: Misformatted DNS query.

dns.BADNAME: Misformatted hostname.

dns.BADFAMILY: Unsupported address family.

dns.BADRESP: Misformatted DNS reply.

dns.CONNREFUSED: Could not contact DNS servers.

dns.TIMEOUT: Timeout while contacting DNS servers.

dns.EOF: End of file.

dns.FILE: Error reading file.

dns.NOMEM: Out of memory.

dns.DESTRUCTION: Channel is being destroyed.

dns.BADSTR: Misformatted string.

dns.BADFLAGS: Illegal flags specified.

dns.NONAME: Given hostname is not numeric.

dns.BADHINTS: Illegal hints flags specified.

dns.NOTINITIALIZED: c-ares library initialization not yet performed.

dns.LOADIPHLPAPI: Error loading iphlpapi.dll.

dns.ADDRGETNETWORKPARAMS: Could not find GetNetworkParams
function.
dns.CANCELLED: DNS query cancelled.

Implementation considerations#
Although dns.lookup() and the
various dns.resolve*()/dns.reverse() functions have the same goal of
associating a network name with a network address (or vice versa), their
behavior is quite different. These differences can have subtle but
significant consequences on the behavior of Node.js programs.
dns.lookup()#
Under the hood, dns.lookup() uses the same operating system facilities as
most other programs. For instance, dns.lookup() will almost always resolve
a given name the same way as the ping command. On most POSIX-like
operating systems, the behavior of the dns.lookup() function can be
modified by changing settings in nsswitch.conf(5) and/or resolv.conf(5),
but note that changing these files will change the behavior of all other
programs running on the same operating system.
Though the call to dns.lookup() will be asynchronous from JavaScript's
perspective, it is implemented as a synchronous call to getaddrinfo(3) that
runs on libuv's threadpool. Because libuv's threadpool has a fixed size, it
means that if for whatever reason the call to getaddrinfo(3) takes a long
time, other operations that could run on libuv's threadpool (such as
filesystem operations) will experience degraded performance. In order to
mitigate this issue, one potential solution is to increase the size of libuv's
threadpool by setting the 'UV_THREADPOOL_SIZE' environment variable to
a value greater than 4(its current default value). For more information on
libuv's threadpool, see the official libuv documentation.
dns.resolve(), dns.resolve*() and dns.reverse()#
These functions are implemented quite differently than dns.lookup(). They
do not use getaddrinfo(3) and they always perform a DNS query on the

network. This network communication is always done asynchronously, and

does not use libuv's threadpool.
As a result, these functions cannot have the same negative impact on
other processing that happens on libuv's threadpool that dns.lookup() can
have.
They do not use the same set of configuration files than
what dns.lookup() uses. For instance, they do not use the configuration
from /etc/hosts.

Domain#
Stability: 0 - Deprecated
This module is pending deprecation. Once a replacement API has
been finalized, this module will be fully deprecated. Most end users
should not have cause to use this module. Users who absolutely must
have the functionality that domains provide may rely on it for the time
being but should expect to have to migrate to a different solution in the
future.
Domains provide a way to handle multiple different IO operations as a
single group. If any of the event emitters or callbacks registered to a
domain emit an'error' event, or throw an error, then the domain object will
be notified, rather than losing the context of the error in
theprocess.on('uncaughtException') handler, or causing the program to
exit immediately with an error code.
Warning: Don't Ignore Errors!#
Domain error handlers are not a substitute for closing down your process
when an error occurs.
By the very nature of how throw works in JavaScript, there is almost never
any way to safely "pick up where you left off", without leaking references,
or creating some other sort of undefined brittle state.

The safest way to respond to a thrown error is to shut down the process.
Of course, in a normal web server, you might have many connections
open, and it is not reasonable to abruptly shut those down because an
error was triggered by someone else.
The better approach is to send an error response to the request that
triggered the error, while letting the others finish in their normal time, and
stop listening for new requests in that worker.
In this way, domain usage goes hand-in-hand with the cluster module,
since the master process can fork a new worker when a worker
encounters an error. For Node.js programs that scale to multiple machines,
the terminating proxy or service registry can take note of the failure, and
react accordingly.
For example, this is not a good idea:
// XXX WARNING! BAD IDEA!
var d = require('domain').create();
d.on('error', (er) => {
// The error won't crash the process, but what it does is worse!
// Though we've prevented abrupt process restarting, we are leaking
// resources like crazy if this ever happens.
// This is no better than process.on('uncaughtException')!
console.log('error, but oh well', er.message);
});
d.run(() => {
require('http').createServer((req, res) => {
handleRequest(req, res);
}).listen(PORT);
});
By using the context of a domain, and the resilience of separating our
program into multiple worker processes, we can react more appropriately,
and handle errors with much greater safety.
// Much better!
const cluster = require('cluster');

const PORT = +process.env.PORT || 1337;

if (cluster.isMaster) {
// In real life, you'd probably use more than just 2 workers,
// and perhaps not put the master and worker in the same file.
//
// You can also of course get a bit fancier about logging, and
// implement whatever custom logic you need to prevent DoS
// attacks and other bad behavior.
//
// See the options in the cluster documentation.
//
// The important thing is that the master does very little,
// increasing our resilience to unexpected errors.
cluster.fork();
cluster.fork();
cluster.on('disconnect', (worker) => {
console.error('disconnect!');
cluster.fork();
});
} else {
// the worker
//
// This is where we put our bugs!
const domain = require('domain');
// See the cluster documentation for more details about using
// worker processes to serve requests. How it works, caveats, etc.
const server = require('http').createServer((req, res) => {
var d = domain.create();
d.on('error', (er) => {
console.error('error', er.stack);

//
//
//
//

Note: we're in dangerous territory!

By definition, something unexpected occurred,
which we probably didn't want.
Anything can happen now! Be very careful!

try {
// make sure we close down within 30 seconds
var killtimer = setTimeout(() => {
process.exit(1);
}, 30000);
// But don't keep the process open just for that!
killtimer.unref();
// stop taking new requests.
server.close();
// Let the master know we're dead. This will trigger a
// 'disconnect' in the cluster master, and then it will fork
// a new worker.
cluster.worker.disconnect();
// try to send an error to the request that triggered the problem
res.statusCode = 500;
res.setHeader('content-type', 'text/plain');
res.end('Oops, there was a problem!\n');
} catch (er2) {
// oh well, not much we can do at this point.
console.error('Error sending 500!', er2.stack);
}
});
// Because req and res were created before this domain existed,
// we need to explicitly add them.
// See the explanation of implicit vs explicit binding below.
d.add(req);
d.add(res);
// Now run the handler function in the domain.

d.run(() => {
handleRequest(req, res);
});
});
server.listen(PORT);
}
// This part isn't important. Just an example routing thing.
// You'd put your fancy application logic here.
function handleRequest(req, res) {
switch(req.url) {
case '/error':
// We do some async stuff, and then...
setTimeout(() => {
// Whoops!
flerb.bark();
});
break;
default:
res.end('ok');
}
}
Additions to Error objects#
Any time an Error object is routed through a domain, a few extra fields are
added to it.

error.domain The domain that first handled the error.

error.domainEmitter The event emitter that emitted an 'error' event

with the error object.

error.domainBound The callback function which was bound to the

domain, and passed an error as its first argument.

error.domainThrown A boolean indicating whether the error was

thrown, emitted, or passed to a bound callback function.

Implicit Binding#

If domains are in use, then all new EventEmitter objects (including Stream
objects, requests, responses, etc.) will be implicitly bound to the active
domain at the time of their creation.
Additionally, callbacks passed to lowlevel event loop requests (such as to
fs.open, or other callback-taking methods) will automatically be bound to
the active domain. If they throw, then the domain will catch the error.
In order to prevent excessive memory usage, Domain objects themselves
are not implicitly added as children of the active domain. If they were,
then it would be too easy to prevent request and response objects from
being properly garbage collected.
If you want to nest Domain objects as children of a parent Domain, then
you must explicitly add them.
Implicit binding routes thrown errors and 'error' events to the
Domain's 'error' event, but does not register the EventEmitter on the
Domain, sodomain.dispose() will not shut down the EventEmitter. Implicit
binding only takes care of thrown errors and 'error' events.
Explicit Binding#
Sometimes, the domain in use is not the one that ought to be used for a
specific event emitter. Or, the event emitter could have been created in
the context of one domain, but ought to instead be bound to some other
domain.
For example, there could be one domain in use for an HTTP server, but
perhaps we would like to have a separate domain to use for each request.
That is possible via explicit binding.
For example:
// create a top-level domain for the server
const domain = require('domain');
const http = require('http');
const serverDomain = domain.create();
serverDomain.run(() => {

// server is created in the scope of serverDomain

http.createServer((req, res) => {
// req and res are also created in the scope of serverDomain
// however, we'd prefer to have a separate domain for each request.
// create it first thing, and add req and res to it.
var reqd = domain.create();
reqd.add(req);
reqd.add(res);
reqd.on('error', (er) => {
console.error('Error', er, req.url);
try {
res.writeHead(500);
res.end('Error occurred, sorry.');
} catch (er) {
console.error('Error sending 500', er, req.url);
}
});
}).listen(1337);
});
domain.create()#

return: <Domain>

Returns a new Domain object.

Class: Domain#
The Domain class encapsulates the functionality of routing errors and
uncaught exceptions to the active Domain object.
Domain is a child class of EventEmitter. To handle the errors that it
catches, listen to its 'error' event.
domain.run(fn[, arg][, ...])#

fn <Function>

Run the supplied function in the context of the domain, implicitly binding
all event emitters, timers, and lowlevel requests that are created in that
context. Optionally, arguments can be passed to the function.

This is the most basic way to use a domain.

Example:
const domain = require('domain');
const fs = require('fs');
const d = domain.create();
d.on('error', (er) => {
console.error('Caught error!', er);
});
d.run(() => {
process.nextTick(() => {
setTimeout(() => { // simulating some various async stuff
fs.open('non-existent file', 'r', (er, fd) => {
if (er) throw er;
// proceed...
});
}, 100);
});
});
In this example, the d.on('error') handler will be triggered, rather than
crashing the program.
domain.members#

<Array>

An array of timers and event emitters that have been explicitly added to
the domain.
domain.add(emitter)#

emitter <EventEmitter> | <Timer> emitter or timer to be added to

the domain

Explicitly adds an emitter to the domain. If any event handlers called by

the emitter throw an error, or if the emitter emits an 'error' event, it will
be routed to the domain's 'error' event, just like with implicit binding.

This also works with timers that are returned

from setInterval() and setTimeout(). If their callback function throws, it will
be caught by the domain 'error' handler.
If the Timer or EventEmitter was already bound to a domain, it is removed
from that one, and bound to this one instead.
domain.remove(emitter)#

emitter <EventEmitter> | <Timer> emitter or timer to be removed

from the domain

The opposite of domain.add(emitter). Removes domain handling from the

specified emitter.
domain.bind(callback)#

callback <Function> The callback function

return: <Function> The bound function

The returned function will be a wrapper around the supplied callback

function. When the returned function is called, any errors that are thrown
will be routed to the domain's 'error' event.
Example#

const d = domain.create();
function readSomeFile(filename, cb) {
fs.readFile(filename, 'utf8', d.bind((er, data) => {
// if this throws, it will also be passed to the domain
return cb(er, data ? JSON.parse(data) : null);
}));
}
d.on('error', (er) => {
// an error occurred somewhere.
// if we throw it now, it will crash the program
// with the normal line number and stack message.
});

domain.intercept(callback)#

callback <Function> The callback function

return: <Function> The intercepted function

This method is almost identical to domain.bind(callback). However, in

addition to catching thrown errors, it will also intercept Error objects sent
as the first argument to the function.
In this way, the common if (err) return callback(err); pattern can be
replaced with a single error handler in a single place.
Example#

const d = domain.create();
function readSomeFile(filename, cb) {
fs.readFile(filename, 'utf8', d.intercept((data) => {
// note, the first argument is never passed to the
// callback since it is assumed to be the 'Error' argument
// and thus intercepted by the domain.
// if this throws, it will also be passed to the domain
// so the error-handling logic can be moved to the 'error'
// event on the domain instead of being repeated throughout
// the program.
return cb(null, JSON.parse(data));
}));
}
d.on('error', (er) => {
// an error occurred somewhere.
// if we throw it now, it will crash the program
// with the normal line number and stack message.
});
domain.enter()#
The enter method is plumbing used by the run, bind,
and intercept methods to set the active domain. It

sets domain.active and process.domain to the domain, and implicitly

pushes the domain onto the domain stack managed by the domain
module (see domain.exit() for details on the domain stack). The call
to enter delimits the beginning of a chain of asynchronous calls and I/O
operations bound to a domain.
Calling enter changes only the active domain, and does not alter the
domain itself. enter and exit can be called an arbitrary number of times on
a single domain.
If the domain on which enter is called has been disposed, enter will return
without setting the domain.
domain.exit()#
The exit method exits the current domain, popping it off the domain stack.
Any time execution is going to switch to the context of a different chain of
asynchronous calls, it's important to ensure that the current domain is
exited. The call to exit delimits either the end of or an interruption to the
chain of asynchronous calls and I/O operations bound to a domain.
If there are multiple, nested domains bound to the current execution
context, exit will exit any domains nested within this domain.
Calling exit changes only the active domain, and does not alter the
domain itself. enter and exit can be called an arbitrary number of times on
a single domain.
If the domain on which exit is called has been disposed, exit will return
without exiting the domain.
domain.dispose()#
Stability: 0 - Deprecated. Please recover from failed IO actions
explicitly via error event handlers set on the domain.
Once dispose has been called, the domain will no longer be used by
callbacks bound into the domain via run, bind, or intercept, and
a 'dispose'event is emitted.

Errors#
Applications running in Node.js will generally experience four categories of
errors:

Standard JavaScript errors such as:

o
o

<SyntaxError> : thrown in response to improper JavaScript

language syntax.

<RangeError> : thrown when a value is not within an

expected range

<EvalError> : thrown when a call to eval() fails.

<ReferenceError> : thrown when using undefined variables

<TypeError> : thrown when passing arguments of the wrong

type

<URIError> : thrown when a global URI handling function is

misused.

System errors triggered by underlying operating system constraints

such as attempting to open a file that does not exist, attempting to
send data over a closed socket, etc;
And User-specified errors triggered by application code.
Assertion Errors are a special class of error that can be triggered
whenever Node.js detects an exceptional logic violation that should
never occur. These are raised typically by the assert module.

All JavaScript and System errors raised by Node.js inherit from, or are
instances of, the standard JavaScript <Error> class and are guaranteed to
provide at least the properties available on that class.
Error Propagation and Interception#
Node.js supports several mechanisms for propagating and handling errors
that occur while an application is running. How these errors are reported
and handled depends entirely on the type of Error and the style of the API
that is called.

All JavaScript errors are handled as exceptions that immediately generate

and throw an error using the standard JavaScript throw mechanism. These
are handled using the try / catch construct provided by the JavaScript
language.
// Throws with a ReferenceError because z is undefined
try {
const m = 1;
const n = m + z;
} catch (err) {
// Handle the error here.
}
Any use of the JavaScript throw mechanism will raise an exception
that must be handled using try / catch or the Node.js process will exit
immediately.
With few exceptions, Synchronous APIs (any blocking method that does
not accept a callback function, such as fs.readFileSync), will use throw to
report errors.
Errors that occur within Asynchronous APIs may be reported in multiple
ways:
Most asynchronous methods that accept a callback function will

accept an Error object passed as the first argument to that function. If

that first argument is not null and is an instance of Error, then an error
occurred that should be handled.

const fs = require('fs');
fs.readFile('a file that does not exist', (err, data) => {
if (err) {
console.error('There was an error reading the file!', err);
return;
}
// Otherwise handle the data
});
When an asynchronous method is called on an object that is
an EventEmitter, errors can be routed to that object's 'error' event.

const net = require('net');

const connection = net.connect('localhost');

// Adding an 'error' event handler to a stream:

connection.on('error', (err) => {
// If the connection is reset by the server, or if it can't
// connect at all, or on any sort of error encountered by
// the connection, the error will be sent here.
console.error(err);
});

connection.pipe(process.stdout);
A handful of typically asynchronous methods in the Node.js API may
still use the throw mechanism to raise exceptions that must be
handled usingtry / catch. There is no comprehensive list of such
methods; please refer to the documentation of each method to
determine the appropriate error handling mechanism required.

The use of the 'error' event mechanism is most common for streambased and event emitter-based APIs, which themselves represent a series
of asynchronous operations over time (as opposed to a single operation
that may pass or fail).
For all EventEmitter objects, if an 'error' event handler is not provided, the
error will be thrown, causing the Node.js process to report an unhandled
exception and crash unless either: The domain module is used
appropriately or a handler has been registered for
the process.on('uncaughtException')event.
const EventEmitter = require('events');
const ee = new EventEmitter();
setImmediate(() => {
// This will crash the process because no 'error' event
// handler has been added.
ee.emit('error', new Error('This will crash'));
});

Errors generated in this way cannot be intercepted using try / catch as

they are thrown after the calling code has already exited.
Developers must refer to the documentation for each method to
determine exactly how errors raised by those methods are propagated.
Node.js style callbacks#
Most asynchronous methods exposed by the Node.js core API follow an
idiomatic pattern referred to as a "Node.js style callback". With this
pattern, a callback function is passed to the method as an argument.
When the operation either completes or an error is raised, the callback
function is called with the Error object (if any) passed as the first
argument. If no error was raised, the first argument will be passed as null.
const fs = require('fs');
function nodeStyleCallback(err, data) {
if (err) {
console.error('There was an error', err);
return;
}
console.log(data);
}
fs.readFile('/some/file/that/does-not-exist', nodeStyleCallback);
fs.readFile('/some/file/that/does-exist', nodeStyleCallback)
The JavaScript try / catch mechanism cannot be used to intercept errors
generated by asynchronous APIs. A common mistake for beginners is to
try to use throw inside a Node.js style callback:
// THIS WILL NOT WORK:
const fs = require('fs');
try {
fs.readFile('/some/file/that/does-not-exist', (err, data) => {
// mistaken assumption: throwing here...
if (err) {
throw err;

}
});
} catch(err) {
// This will not catch the throw!
console.log(err);
}
This will not work because the callback function passed to fs.readFile() is
called asynchronously. By the time the callback has been called, the
surrounding code (including the try { } catch(err) { } block will have
already exited. Throwing an error inside the callback can crash the
Node.js process in most cases. If domains are enabled, or a handler has
been registered with process.on('uncaughtException'), such errors can be
intercepted.
Class: Error#
A generic JavaScript Error object that does not denote any specific
circumstance of why the error occurred. Error objects capture a "stack
trace" detailing the point in the code at which the Error was instantiated,
and may provide a text description of the error.
All errors generated by Node.js, including all System and JavaScript errors,
will either be instances of, or inherit from, the Error class.
new Error(message)#
Creates a new Error object and sets the error.message property to the
provided text message. If an object is passed as message, the text
message is generated by calling message.toString().
The error.stack property will represent the point in the code at which new
Error() was called. Stack traces are dependent on V8's stack trace API.
Stack traces extend only to either (a) the beginning of synchronous code
execution, or (b) the number of frames given by the
property Error.stackTraceLimit, whichever is smaller.

Error.captureStackTrace(targetObject[, constructorOpt])#
Creates a .stack property on targetObject, which when accessed returns a
string representing the location in the code at
whichError.captureStackTrace() was called.
const myObject = {};
Error.captureStackTrace(myObject);
myObject.stack // similar to `new Error().stack`
The first line of the trace, instead of being prefixed with ErrorType:
message, will be the result of calling targetObject.toString().
The optional constructorOpt argument accepts a function. If given, all
frames above constructorOpt, including constructorOpt, will be omitted
from the generated stack trace.
The constructorOpt argument is useful for hiding implementation details
of error generation from an end user. For instance:
function MyError() {
Error.captureStackTrace(this, MyError);
}
// Without passing MyError to captureStackTrace, the MyError
// frame would should up in the .stack property. by passing
// the constructor, we omit that frame and all frames above it.
new MyError().stack
Error.stackTraceLimit#
The Error.stackTraceLimit property specifies the number of stack frames
collected by a stack trace (whether generated by new
Error().stack orError.captureStackTrace(obj)).
The default value is 10 but may be set to any valid JavaScript number.
Changes will affect any stack trace captured after the value has been
changed.
If set to a non-number value, or set to a negative number, stack traces
will not capture any frames.

error.message#

Returns the string description of error as set by calling new

Error(message). The message passed to the constructor will also appear in
the first line of the stack trace of the Error, however changing this
property after the Error object is created may not change the first line of
the stack trace.
const err = new Error('The message');
console.log(err.message);
// Prints: The message

error.stack#

Returns a string describing the point in the code at which the Error was
instantiated.
For example:
Error: Things keep happening!
at /home/gbusey/file.js:525:2
at Frobnicator.refrobulate (/home/gbusey/business-logic.js:424:21)
at Actor.<anonymous> (/home/gbusey/actors.js:400:8)
at increaseSynergy (/home/gbusey/actors.js:701:6)
The first line is formatted as <error class name>: <error message>, and
is followed by a series of stack frames (each line beginning with "at ").
Each frame describes a call site within the code that lead to the error
being generated. V8 attempts to display a name for each function (by
variable name, function name, or object method name), but occasionally it
will not be able to find a suitable name. If V8 cannot determine a name for
the function, only location information will be displayed for that frame.
Otherwise, the determined function name will be displayed with location
information appended in parentheses.
It is important to note that frames are only generated for JavaScript
functions. If, for example, execution synchronously passes through a C++
addon function called cheetahify, which itself calls a JavaScript function,
the frame representing the cheetahify call will not be present in the stack
traces:

const cheetahify = require('./native-binding.node');

function makeFaster() {
// cheetahify *synchronously* calls speedy.
cheetahify(function speedy() {
throw new Error('oh no!');
});
}
makeFaster(); // will throw:
// /home/gbusey/file.js:6
//
throw new Error('oh no!');
//
^
// Error: oh no!
//
at speedy (/home/gbusey/file.js:6:11)
//
at makeFaster (/home/gbusey/file.js:5:3)
//
at Object.<anonymous> (/home/gbusey/file.js:10:1)
//
at Module._compile (module.js:456:26)
//
at Object.Module._extensions..js (module.js:474:10)
//
at Module.load (module.js:356:32)
//
at Function.Module._load (module.js:312:12)
//
at Function.Module.runMain (module.js:497:10)
//
at startup (node.js:119:16)
//
at node.js:906:3
The location information will be one of:

native, if the frame represents a call internal to V8 (as in [].forEach).

plain-filename.js:line:column, if the frame represents a call internal

to Node.js.

/absolute/path/to/file.js:line:column, if the frame represents a call in

a user program, or its dependencies.

The string representing the stack trace is lazily generated when

the error.stack property is accessed.

The number of frames captured by the stack trace is bounded by the

smaller of Error.stackTraceLimit or the number of available frames on the
current event loop tick.
System-level errors are generated as augmented Error instances, which
are detailed here.
Class: RangeError#
A subclass of Error that indicates that a provided argument was not within
the set or range of acceptable values for a function; whether that is a
numeric range, or outside the set of options for a given function
parameter.
For example:
require('net').connect(-1);
// throws RangeError, port should be > 0 && < 65536
Node.js will generate and throw RangeError instances immediately as a
form of argument validation.
Class: ReferenceError#
A subclass of Error that indicates that an attempt is being made to access
a variable that is not defined. Such errors commonly indicate typos in
code, or an otherwise broken program.
While client code may generate and propagate these errors, in practice,
only V8 will do so.
doesNotExist;
// throws ReferenceError, doesNotExist is not a variable in this
program.
ReferenceError instances will have an error.arguments property whose
value is an array containing a single element: a string representing the
variable that was not defined.
const assert = require('assert');
try {

doesNotExist;
} catch(err) {
assert(err.arguments[0], 'doesNotExist');
}
Unless an application is dynamically generating and running
code, ReferenceError instances should always be considered a bug in the
code or its dependencies.
Class: SyntaxError#
A subclass of Error that indicates that a program is not valid JavaScript.
These errors may only be generated and propagated as a result of code
evaluation. Code evaluation may happen as a result
of eval, Function, require, or vm. These errors are almost always indicative
of a broken program.
try {
require('vm').runInThisContext('binary ! isNotOk');
} catch(err) {
// err will be a SyntaxError
}
SyntaxError instances are unrecoverable in the context that created them
they may only be caught by other contexts.
Class: TypeError#
A subclass of Error that indicates that a provided argument is not an
allowable type. For example, passing a function to a parameter which
expects a string would be considered a TypeError.
require('url').parse(() => { });
// throws TypeError, since it expected a string
Node.js will generate and throw TypeError instances immediately as a
form of argument validation.
Exceptions vs. Errors#

A JavaScript exception is a value that is thrown as a result of an invalid

operation or as the target of a throw statement. While it is not required
that these values are instances of Error or classes which inherit from Error,
all exceptions thrown by Node.js or the JavaScript runtime will be
instances of Error.
Some exceptions are unrecoverable at the JavaScript layer. Such
exceptions will always cause the Node.js process to crash. Examples
include assert()checks or abort() calls in the C++ layer.
System Errors#
System errors are generated when exceptions occur within the program's
runtime environment. Typically, these are operational errors that occur
when an application violates an operating system constraint such as
attempting to read a file that does not exist or when the user does not
have sufficient permissions.
System errors are typically generated at the syscall level: an exhaustive
list of error codes and their meanings is available by running man 2
intro or man 3 errno on most Unices; or online.
In Node.js, system errors are represented as augmented Error objects with
added properties.
Class: System Error#
error.code#
error.errno#

Returns a string representing the error code, which is always E followed by

a sequence of capital letters, and may be referenced in man 2 intro.
The properties error.code and error.errno are aliases of one another and
return the same value.
error.syscall#

Returns a string describing the syscall that failed.

Common System Errors#

This list is not exhaustive, but enumerates many of the common system
errors encountered when writing a Node.js program. An exhaustive list
may be found here.

EACCES (Permission denied): An attempt was made to access a file

in a way forbidden by its file access permissions.

EADDRINUSE (Address already in use): An attempt to bind a server

(net, http, or https) to a local address failed due to another server on
the local system already occupying that address.

ECONNREFUSED (Connection refused): No connection could be

made because the target machine actively refused it. This usually
results from trying to connect to a service that is inactive on the
foreign host.

ECONNRESET (Connection reset by peer): A connection was forcibly

closed by a peer. This normally results from a loss of the connection
on the remote socket due to a timeout or reboot. Commonly
encountered via the http and net modules.

EEXIST (File exists): An existing file was the target of an operation

that required that the target not exist.

EISDIR (Is a directory): An operation expected a file, but the given

pathname was a directory.

EMFILE (Too many open files in system): Maximum number of file

descriptors allowable on the system has been reached, and requests
for another descriptor cannot be fulfilled until at least one has been
closed. This is encountered when opening many files at once in
parallel, especially on systems (in particular, OS X) where there is a
low file descriptor limit for processes. To remedy a low limit, run ulimit
-n 2048 in the same shell that will run the Node.js process.

ENOENT (No such file or directory): Commonly raised

by fs operations to indicate that a component of the specified

pathname does not exist -- no entity (file or directory) could be found

by the given path.

ENOTDIR (Not a directory): A component of the given pathname

existed, but was not a directory as expected. Commonly raised
by fs.readdir.

ENOTEMPTY (Directory not empty): A directory with entries was the

target of an operation that requires an empty directory -usually fs.unlink.

EPERM (Operation not permitted): An attempt was made to perform

an operation that requires elevated privileges.

EPIPE (Broken pipe): A write on a pipe, socket, or FIFO for which

there is no process to read the data. Commonly encountered at
the net and httplayers, indicative that the remote side of the stream
being written to has been closed.

ETIMEDOUT (Operation timed out): A connect or send request failed

because the connected party did not properly respond after a period
of time. Usually encountered by http or net -- often a sign that
a socket.end() was not properly called.

Events#
Stability: 2 - Stable
Much of the Node.js core API is built around an idiomatic asynchronous
event-driven architecture in which certain kinds of objects (called
"emitters") periodically emit named events that cause Function objects
("listeners") to be called.
For instance: a net.Server object emits an event each time a peer
connects to it; a fs.ReadStream emits an event when the file is opened;
a stream emits an event whenever data is available to be read.

All objects that emit events are instances of the EventEmitter class. These
objects expose an eventEmitter.on() function that allows one or more
Functions to be attached to named events emitted by the object. Typically,
event names are camel-cased strings but any valid JavaScript property
key can be used.
When the EventEmitter object emits an event, all of the Functions
attached to that specific event are called synchronously. Any values
returned by the called listeners are ignored and will be discarded.
The following example shows a simple EventEmitter instance with a single
listener. The eventEmitter.on() method is used to register listeners, while
the eventEmitter.emit() method is used to trigger the event.
const EventEmitter = require('events');
class MyEmitter extends EventEmitter {}
const myEmitter = new MyEmitter();
myEmitter.on('event', () => {
console.log('an event occurred!');
});
myEmitter.emit('event');
Passing arguments and this to listeners#
The eventEmitter.emit() method allows an arbitrary set of arguments to be
passed to the listener functions. It is important to keep in mind that when
an ordinary listener function is called by the EventEmitter, the
standard this keyword is intentionally set to reference the EventEmitter to
which the listener is attached.
const myEmitter = new MyEmitter();
myEmitter.on('event', function(a, b) {
console.log(a, b, this);
// Prints:
// a b MyEmitter {
//
domain: null,
//
_events: { event: [Function] },
//
_eventsCount: 1,

//
_maxListeners: undefined }
});
myEmitter.emit('event', 'a', 'b');
It is possible to use ES6 Arrow Functions as listeners, however, when doing
so, the this keyword will no longer reference the EventEmitter instance:
const myEmitter = new MyEmitter();
myEmitter.on('event', (a, b) => {
console.log(a, b, this);
// Prints: a b {}
});
myEmitter.emit('event', 'a', 'b');
Asynchronous vs. Synchronous#
The EventListener calls all listeners synchronously in the order in which
they were registered. This is important to ensure the proper sequencing of
events and to avoid race conditions or logic errors. When appropriate,
listener functions can switch to an asynchronous mode of operation using
thesetImmediate() or process.nextTick() methods:
const myEmitter = new MyEmitter();
myEmitter.on('event', (a, b) => {
setImmediate(() => {
console.log('this happens asynchronously');
});
});
myEmitter.emit('event', 'a', 'b');
Handling events only once#
When a listener is registered using the eventEmitter.on() method, that
listener will be invoked every time the named event is emitted.
const myEmitter = new MyEmitter();
var m = 0;
myEmitter.on('event', () => {
console.log(++m);
});

myEmitter.emit('event');
// Prints: 1
myEmitter.emit('event');
// Prints: 2
Using the eventEmitter.once() method, it is possible to register a listener
that is unregistered before it is called.
const myEmitter = new MyEmitter();
var m = 0;
myEmitter.once('event', () => {
console.log(++m);
});
myEmitter.emit('event');
// Prints: 1
myEmitter.emit('event');
// Ignored
Error events#
When an error occurs within an EventEmitter instance, the typical action is
for an 'error' event to be emitted. These are treated as a special case
within Node.js.
If an EventEmitter does not have at least one listener registered for
the 'error' event, and an 'error' event is emitted, the error is thrown, a
stack trace is printed, and the Node.js process exits.
const myEmitter = new MyEmitter();
myEmitter.emit('error', new Error('whoops!'));
// Throws and crashes Node.js
To guard against crashing the Node.js process, developers can either
register a listener for the process.on('uncaughtException') event or use
thedomain module (Note, however, that the domain module has been
deprecated).
const myEmitter = new MyEmitter();
process.on('uncaughtException', (err) => {

console.log('whoops! there was an error');

});
myEmitter.emit('error', new Error('whoops!'));
// Prints: whoops! there was an error
As a best practice, developers should always register listeners for
the 'error' event:
const myEmitter = new MyEmitter();
myEmitter.on('error', (err) => {
console.log('whoops! there was an error');
});
myEmitter.emit('error', new Error('whoops!'));
// Prints: whoops! there was an error
Class: EventEmitter#
The EventEmitter class is defined and exposed by the events module:
const EventEmitter = require('events');
All EventEmitters emit the event 'newListener' when new listeners are
added and 'removeListener' when a listener is removed.
Event: 'newListener'#

eventName <String> | <Symbol> The name of the event being

listened for
listener <Function> The event handler function

The EventEmitter instance will emit it's own 'newListener' event before a
listener is added to it's internal array of listeners.
Listeners registered for the 'newListener' event will be passed the event
name and a reference to the listener being added.
The fact that the event is triggered before adding the listener has a subtle
but important side effect: any additional listeners registered to the
same namewithin the 'newListener' callback will be inserted before the
listener that is in the process of being added.

const myEmitter = new MyEmitter();

// Only do this once so we don't loop forever
myEmitter.once('newListener', (event, listener) => {
if (event === 'event') {
// Insert a new listener in front
myEmitter.on('event', () => {
console.log('B');
});
}
});
myEmitter.on('event', () => {
console.log('A');
});
myEmitter.emit('event');
// Prints:
// B
// A
Event: 'removeListener'#

eventName <String> | <Symbol> The event name

listener <Function> The event handler function

The 'removeListener' event is emitted after a listener is removed.

EventEmitter.listenerCount(emitter, eventName)#
Stability: 0 - Deprecated: Use emitter.listenerCount() instead.
A class method that returns the number of listeners for the
given eventName registered on the given emitter.
const myEmitter = new MyEmitter();
myEmitter.on('event', () => {});
myEmitter.on('event', () => {});
console.log(EventEmitter.listenerCount(myEmitter, 'event'));
// Prints: 2
EventEmitter.defaultMaxListeners#
By default, a maximum of 10 listeners can be registered for any single
event. This limit can be changed for individual EventEmitter instances

using theemitter.setMaxListeners(n) method. To change the default

for all EventEmitter instances,
the EventEmitter.defaultMaxListeners property can be used.
Take caution when setting the EventEmitter.defaultMaxListeners because
the change effects all EventEmitter instances, including those created
before the change is made. However,
calling emitter.setMaxListeners(n) still has precedence
over EventEmitter.defaultMaxListeners.
Note that this is not a hard limit. The EventEmitter instance will allow
more listeners to be added but will output a trace warning to stderr
indicating that a possible EventEmitter memory leak has been detected.
For any single EventEmitter,
the emitter.getMaxListeners() andemitter.setMaxListeners() methods can
be used to temporarily avoid this warning:
emitter.setMaxListeners(emitter.getMaxListeners() + 1);
emitter.once('event', () => {
// do stuff
emitter.setMaxListeners(Math.max(emitter.getMaxListeners() - 1, 0));
});
emitter.addListener(eventName, listener)#
Alias for emitter.on(eventName, listener).
emitter.emit(eventName[, arg1][, arg2][, ...])#
Synchronously calls each of the listeners registered for the event
named eventName, in the order they were registered, passing the
supplied arguments to each.
Returns true if the event had listeners, false otherwise.
emitter.eventNames()#
Returns an array listing the events for which the emitter has registered
listeners. The values in the array will be strings or Symbols.
const EventEmitter = require('events');
const myEE = new EventEmitter();

myEE.on('foo', () => {});

myEE.on('bar', () => {});
const sym = Symbol('symbol');
myEE.on(sym, () => {});
console.log(myEE.eventNames());
// Prints [ 'foo', 'bar', Symbol(symbol) ]
emitter.getMaxListeners()#
Returns the current max listener value for the EventEmitter which is either
set by emitter.setMaxListeners(n) or defaults
toEventEmitter.defaultMaxListeners.
emitter.listenerCount(eventName)#

eventName <Value> The name of the event being listened for

Returns the number of listeners listening to the event named eventName.

emitter.listeners(eventName)#
Returns a copy of the array of listeners for the event named eventName.
server.on('connection', (stream) => {
console.log('someone connected!');
});
console.log(util.inspect(server.listeners('connection')));
// Prints: [ [Function] ]
emitter.on(eventName, listener)#

eventName <string> | <Symbol> The name of the event.

listener <Function> The callback function

Adds the listener function to the end of the listeners array for the event
named eventName. No checks are made to see if the listener has already
been added. Multiple calls passing the same combination
of eventName and listener will result in the listener being added, and
called, multiple times.
server.on('connection', (stream) => {

console.log('someone connected!');
});
Returns a reference to the EventEmitter so calls can be chained.
By default, event listeners are invoked in the order they are added.
The emitter.prependListener() method can be used as an alternative to
add the event listener to the beginning of the listeners array.
const myEE = new EventEmitter();
myEE.on('foo', () => console.log('a'));
myEE.prependListener('foo', () => console.log('b'));
myEE.emit('foo');
// Prints:
// b
// a
emitter.once(eventName, listener)#

eventName <string> | <Symbol> The name of the event.

listener <Function> The callback function

Adds a one time listener function for the event named eventName. The
next time eventName is triggered, this listener is removed and then
invoked.
server.once('connection', (stream) => {
console.log('Ah, we have our first user!');
});
Returns a reference to the EventEmitter so calls can be chained.
By default, event listeners are invoked in the order they are added.
The emitter.prependOnceListener() method can be used as an alternative
to add the event listener to the beginning of the listeners array.
const myEE = new EventEmitter();
myEE.once('foo', () => console.log('a'));
myEE.prependOnceListener('foo', () => console.log('b'));
myEE.emit('foo');
// Prints:

// b
// a
emitter.prependListener(eventName, listener)#

eventName <string> | <Symbol> The name of the event.

listener <Function> The callback function

Adds the listener function to the beginning of the listeners array for the
event named eventName. No checks are made to see if the listener has
already been added. Multiple calls passing the same combination
of eventName and listener will result in the listener being added, and
called, multiple times.
server.prependListener('connection', (stream) => {
console.log('someone connected!');
});
Returns a reference to the EventEmitter so calls can be chained.
emitter.prependOnceListener(eventName, listener)#

eventName <string> | <Symbol> The name of the event.

listener <Function> The callback function

Adds a one time listener function for the event named eventName to
the beginning of the listeners array. The next time eventName is
triggered, this listener is removed, and then invoked.
server.prependOnceListener('connection', (stream) => {
console.log('Ah, we have our first user!');
});
Returns a reference to the EventEmitter so calls can be chained.
emitter.removeAllListeners([eventName])#
Removes all listeners, or those of the specified eventName.

Note that it is bad practice to remove listeners added elsewhere in the

code, particularly when the EventEmitter instance was created by some
other component or module (e.g. sockets or file streams).
Returns a reference to the EventEmitter so calls can be chained.
emitter.removeListener(eventName, listener)#
Removes the specified listener from the listener array for the event
named eventName.
var callback = (stream) => {
console.log('someone connected!');
};
server.on('connection', callback);
// ...
server.removeListener('connection', callback);
removeListener will remove, at most, one instance of a listener from the
listener array. If any single listener has been added multiple times to the
listener array for the specified eventName, then removeListener must be
called multiple times to remove each instance.
Note that once an event has been emitted, all listeners attached to it at
the time of emitting will be called in order. This implies that
any removeListener()or removeAllListeners() calls after emitting
and before the last listener finishes execution will not remove them
from emit() in progress. Subsequent events will behave as expected.
const myEmitter = new MyEmitter();
var callbackA = () => {
console.log('A');
myEmitter.removeListener('event', callbackB);
};
var callbackB = () => {
console.log('B');
};

myEmitter.on('event', callbackA);
myEmitter.on('event', callbackB);
// callbackA removes listener callbackB but it will still be called.
// Internal listener array at time of emit [callbackA, callbackB]
myEmitter.emit('event');
// Prints:
// A
// B
// callbackB is now removed.
// Internal listener array [callbackA]
myEmitter.emit('event');
// Prints:
// A
Because listeners are managed using an internal array, calling this will
change the position indices of any listener registered after the listener
being removed. This will not impact the order in which listeners are called,
but it will means that any copies of the listener array as returned by
theemitter.listeners() method will need to be recreated.
Returns a reference to the EventEmitter so calls can be chained.
emitter.setMaxListeners(n)#
By default EventEmitters will print a warning if more than 10 listeners are
added for a particular event. This is a useful default that helps finding
memory leaks. Obviously, not all events should be limited to just 10
listeners. The emitter.setMaxListeners() method allows the limit to be
modified for this specific EventEmitter instance. The value can be set
to Infinity (or 0) for to indicate an unlimited number of listeners.
Returns a reference to the EventEmitter so calls can be chained.

File System#

Stability: 2 - Stable
File I/O is provided by simple wrappers around standard POSIX functions.
To use this module do require('fs'). All the methods have asynchronous
and synchronous forms.
The asynchronous form always takes a completion callback as its last
argument. The arguments passed to the completion callback depend on
the method, but the first argument is always reserved for an exception. If
the operation was completed successfully, then the first argument will
be null orundefined.
When using the synchronous form any exceptions are immediately
thrown. You can use try/catch to handle exceptions or allow them to
bubble up.
Here is an example of the asynchronous version:
const fs = require('fs');
fs.unlink('/tmp/hello', (err) => {
if (err) throw err;
console.log('successfully deleted /tmp/hello');
});
Here is the synchronous version:
const fs = require('fs');
fs.unlinkSync('/tmp/hello');
console.log('successfully deleted /tmp/hello');
With the asynchronous methods there is no guaranteed ordering. So the
following is prone to error:
fs.rename('/tmp/hello', '/tmp/world', (err) => {
if (err) throw err;
console.log('renamed complete');
});
fs.stat('/tmp/world', (err, stats) => {

if (err) throw err;

console.log(`stats: ${JSON.stringify(stats)}`);
});
It could be that fs.stat is executed before fs.rename. The correct way to do
this is to chain the callbacks.
fs.rename('/tmp/hello', '/tmp/world', (err) => {
if (err) throw err;
fs.stat('/tmp/world', (err, stats) => {
if (err) throw err;
console.log(`stats: ${JSON.stringify(stats)}`);
});
});
In busy processes, the programmer is strongly encouraged to use the
asynchronous versions of these calls. The synchronous versions will block
the entire process until they complete--halting all connections.
The relative path to a filename can be used. Remember, however, that
this path will be relative to process.cwd().
Most fs functions let you omit the callback argument. If you do, a default
callback is used that rethrows errors. To get a trace to the original call site,
set theNODE_DEBUG environment variable:
$ cat script.js
function bad() {
require('fs').readFile('/');
}
bad();
$ env NODE_DEBUG=fs node script.js
fs.js:88
throw backtrace;
^
Error: EISDIR: illegal operation on a directory, read
<stack trace.>
Buffer API#

fs functions support passing and receiving paths as both strings and

Buffers. The latter is intended to make it possible to work with filesystems
that allow for non-UTF-8 filenames. For most typical uses, working with
paths as Buffers will be unnecessary, as the string API converts to and
from UTF-8 automatically.
Note that on certain file systems (such as NTFS and HFS+) filenames will
always be encoded as UTF-8. On such file systems, passing non-UTF-8
encoded Buffers to fs functions will not work as expected.
Class: fs.FSWatcher#
Objects returned from fs.watch() are of this type.
Event: 'change'#

event <String> The type of fs change

filename <String> | <Buffer> The filename that changed (if
relevant/available)

Emitted when something changes in a watched directory or file. See more

details in fs.watch().
The filename argument may not be provided depending on operating
system support. If filename is provided, it will be provided as
a Buffer iffs.watch() is called with it's encoding option set to 'buffer',
otherwise filename will be a string.
fs.watch('./tmp', {encoding: 'buffer'}, (event, filename) => {
if (filename)
console.log(filename);
// Prints: <Buffer ...>
});
Event: 'error'#

error <Error>

Emitted when an error occurs.

watcher.close()#
Stop watching for changes on the given fs.FSWatcher.
Class: fs.ReadStream#
ReadStream is a Readable Stream.
Event: 'open'#

fd <Integer> Integer file descriptor used by the ReadStream.

Emitted when the ReadStream's file is opened.

Event: 'close'#
Emitted when the ReadStream's underlying file descriptor has been closed
using the fs.close() method.
readStream.path#
The path to the file the stream is reading from as specified in the first
argument to fs.createReadStream(). If path is passed as a string,
thenreadStream.path will be a string. If path is passed as a Buffer,
then readStream.path will be a Buffer.
Class: fs.Stats#
Objects returned from fs.stat(), fs.lstat() and fs.fstat() and their
synchronous counterparts are of this type.

stats.isFile()

stats.isDirectory()

stats.isBlockDevice()

stats.isCharacterDevice()

stats.isSymbolicLink() (only valid with fs.lstat())

stats.isFIFO()

stats.isSocket()

For a regular file util.inspect(stats) would return a string very similar to

this:
{
dev: 2114,
ino: 48064969,
mode: 33188,
nlink: 1,
uid: 85,
gid: 100,
rdev: 0,
size: 527,
blksize: 4096,
blocks: 8,
atime: Mon, 10 Oct 2011 23:24:11 GMT,
mtime: Mon, 10 Oct 2011 23:24:11 GMT,
ctime: Mon, 10 Oct 2011 23:24:11 GMT,
birthtime: Mon, 10 Oct 2011 23:24:11 GMT
}
Please note that atime, mtime, birthtime, and ctime are instances
of Date object and to compare the values of these objects you should use
appropriate methods. For most general uses getTime() will return the
number of milliseconds elapsed since 1 January 1970 00:00:00 UTC and
this integer should be sufficient for any comparison, however there are
additional methods which can be used for displaying fuzzy information.
More details can be found in the MDN JavaScript Reference page.
Stat Time Values#
The times in the stat object have the following semantics:

atime "Access Time" - Time when file data last accessed. Changed
by the mknod(2), utimes(2), and read(2) system calls.

mtime "Modified Time" - Time when file data last modified. Changed
by the mknod(2), utimes(2), and write(2) system calls.

ctime "Change Time" - Time when file status was last changed
(inode data modification). Changed by

the chmod(2), chown(2), link(2), mknod(2),rename(2), unlink(2), utime

s(2), read(2), and write(2) system calls.

birthtime "Birth Time" - Time of file creation. Set once when the file
is created. On filesystems where birthtime is not available, this field
may instead hold either the ctime or 1970-01-01T00:00Z (ie, unix
epoch timestamp 0). Note that this value may be greater
than atime or mtime in this case. On Darwin and other FreeBSD
variants, also set if the atime is explicitly set to an earlier value than
the current birthtime using the utimes(2)system call.

Prior to Node v0.12, the ctime held the birthtime on Windows systems.
Note that as of v0.12, ctime is not "creation time", and on Unix systems, it
never was.
Class: fs.WriteStream#
WriteStream is a Writable Stream.
Event: 'open'#

fd <Integer> Integer file descriptor used by the WriteStream.

Emitted when the WriteStream's file is opened.

Event: 'close'#
Emitted when the WriteStream's underlying file descriptor has been closed
using the fs.close() method.
writeStream.bytesWritten#
The number of bytes written so far. Does not include data that is still
queued for writing.
writeStream.path#
The path to the file the stream is writing to as specified in the first
argument to fs.createWriteStream(). If path is passed as a string,
thenwriteStream.path will be a string. If path is passed as a Buffer,
then writeStream.path will be a Buffer.
fs.access(path[, mode], callback)#

path <String> | <Buffer>

mode <Integer>

callback <Function>

Tests a user's permissions for the file specified by path. mode is an

optional integer that specifies the accessibility checks to be performed.
The following constants define the possible values of mode. It is possible
to create a mask consisting of the bitwise OR of two or more values.

fs.F_OK - File is visible to the calling process. This is useful for

determining if a file exists, but says nothing about rwx permissions.
Default if no modeis specified.

fs.R_OK - File can be read by the calling process.

fs.W_OK - File can be written by the calling process.

fs.X_OK - File can be executed by the calling process. This has no

effect on Windows (will behave like fs.F_OK).

The final argument, callback, is a callback function that is invoked with a

possible error argument. If any of the accessibility checks fail, the error
argument will be populated. The following example checks if the
file /etc/passwd can be read and written by the current process.
fs.access('/etc/passwd', fs.R_OK | fs.W_OK, (err) => {
console.log(err ? 'no access!' : 'can read/write');
});
fs.accessSync(path[, mode])#

path <String> | <Buffer>

mode <Integer>

Synchronous version of fs.access(). This throws if any accessibility checks

fail, and does nothing otherwise.
fs.appendFile(file, data[, options], callback)#

file <String> | <Buffer> | <Number> filename or file descriptor

data <String> | <Buffer>

options <Object> | <String>

encoding <String> | <Null> default = 'utf8'

mode <Integer> default = 0o666

flag <String> default = 'a'

callback <Function>

Asynchronously append data to a file, creating the file if it does not yet
exist. data can be a string or a buffer.
Example:
fs.appendFile('message.txt', 'data to append', (err) => {
if (err) throw err;
console.log('The "data to append" was appended to file!');
});
If options is a string, then it specifies the encoding. Example:
fs.appendFile('message.txt', 'data to append', 'utf8', callback);
Any specified file descriptor has to have been opened for appending.
Note: Specified file descriptors will not be closed automatically.
fs.appendFileSync(file, data[, options])#

file <String> | <Buffer> | <Number> filename or file descriptor

data <String> | <Buffer>

options <Object> | <String>

o

encoding <String> | <Null> default = 'utf8'

mode <Integer> default = 0o666

flag <String> default = 'a'

The synchronous version of fs.appendFile(). Returns undefined.

fs.chmod(path, mode, callback)#

path <String> | <Buffer>

mode <Integer>

callback <Function>

Asynchronous chmod(2). No arguments other than a possible exception

are given to the completion callback.
fs.chmodSync(path, mode)#

path <String> | <Buffer>

mode <Integer>

Synchronous chmod(2). Returns undefined.

fs.chown(path, uid, gid, callback)#

path <String> | <Buffer>

uid <Integer>

gid <Integer>

callback <Function>

Asynchronous chown(2). No arguments other than a possible exception

are given to the completion callback.
fs.chownSync(path, uid, gid)#

path <String> | <Buffer>

uid <Integer>

gid <Integer>

Synchronous chown(2). Returns undefined.

fs.close(fd, callback)#

fd <Integer>

callback <Function>

Asynchronous close(2). No arguments other than a possible exception are

given to the completion callback.
fs.closeSync(fd)#

fd <Integer>

Synchronous close(2). Returns undefined.

fs.createReadStream(path[, options])#

path <String> | <Buffer>

options <String> | <Object>

o

flags <String>

encoding <String>

fd <Integer>

mode <Integer>

autoClose <Boolean>

start <Integer>

end <Integer>

Returns a new ReadStream object. (See Readable Stream).

Be aware that, unlike the default value set for highWaterMark on a
readable stream (16 kb), the stream returned by this method has a default
value of 64 kb for the same parameter.
options is an object or string with the following defaults:
{
flags: 'r',
encoding: null,
fd: null,
mode: 0o666,

autoClose: true
}
options can include start and end values to read a range of bytes from the
file instead of the entire file. Both start and end are inclusive and start at
0. The encoding can be any one of those accepted by Buffer.
If fd is specified, ReadStream will ignore the path argument and will use
the specified file descriptor. This means that no 'open' event will be
emitted. Note that fd should be blocking; non-blocking fds should be
passed to net.Socket.
If autoClose is false, then the file descriptor won't be closed, even if
there's an error. It is your responsibility to close it and make sure there's
no file descriptor leak. If autoClose is set to true (default behavior),
on error or end the file descriptor will be closed automatically.
mode sets the file mode (permission and sticky bits), but only if the file
was created.
An example to read the last 10 bytes of a file which is 100 bytes long:
fs.createReadStream('sample.txt', {start: 90, end: 99});
If options is a string, then it specifies the encoding.
fs.createWriteStream(path[, options])#

path <String> | <Buffer>

options <String> | <Object>

o

flags <String>

defaultEncoding <String>

fd <Integer>

mode <Integer>

autoClose <Boolean>

start <Integer>

Returns a new WriteStream object. (See Writable Stream).

options is an object or string with the following defaults:
{
flags: 'w',
defaultEncoding: 'utf8',
fd: null,
mode: 0o666,
autoClose: true
}
options may also include a start option to allow writing data at some
position past the beginning of the file. Modifying a file rather than
replacing it may require a flags mode of r+ rather than the default
mode w. The defaultEncoding can be any one of those accepted by Buffer.
If autoClose is set to true (default behavior) on error or end the file
descriptor will be closed automatically. If autoClose is false, then the file
descriptor won't be closed, even if there's an error. It is your responsibility
to close it and make sure there's no file descriptor leak.
Like ReadStream, if fd is specified, WriteStream will ignore
the path argument and will use the specified file descriptor. This means
that no 'open'event will be emitted. Note that fd should be blocking; nonblocking fds should be passed to net.Socket.
If options is a string, then it specifies the encoding.
fs.exists(path, callback)#
Stability: 0 - Deprecated: Use fs.stat() or fs.access() instead.

path <String> | <Buffer>

callback <Function>

Test whether or not the given path exists by checking with the file system.
Then call the callback argument with either true or false. Example:
fs.exists('/etc/passwd', (exists) => {

console.log(exists ? 'it\'s there' : 'no passwd!');

});
fs.exists() should not be used to check if a file exists before
calling fs.open(). Doing so introduces a race condition since other
processes may change the file's state between the two calls. Instead, user
code should call fs.open() directly and handle the error raised if the file is
non-existent.
fs.existsSync(path)#
Stability: 0 - Deprecated: Use fs.statSync() or fs.accessSync() instead.

path <String> | <Buffer>

Synchronous version of fs.exists(). Returns true if the file

exists, false otherwise.
fs.fchmod(fd, mode, callback)#

fd <Integer>

mode <Integer>

callback <Function>

Asynchronous fchmod(2). No arguments other than a possible exception

are given to the completion callback.
fs.fchmodSync(fd, mode)#

fd <Integer>

mode <Integer>

Synchronous fchmod(2). Returns undefined.

fs.fchown(fd, uid, gid, callback)#

fd <Integer>

uid <Integer>

gid <Integer>

callback <Function>

Asynchronous fchown(2). No arguments other than a possible exception

are given to the completion callback.
fs.fchownSync(fd, uid, gid)#

fd <Integer>

uid <Integer>

gid <Integer>

Synchronous fchown(2). Returns undefined.

fs.fdatasync(fd, callback)#

fd <Integer>

callback <Function>

Asynchronous fdatasync(2). No arguments other than a possible exception

are given to the completion callback.
fs.fdatasyncSync(fd)#

fd <Integer>

Synchronous fdatasync(2). Returns undefined.

fs.fstat(fd, callback)#

fd <Integer>

callback <Function>

Asynchronous fstat(2). The callback gets two arguments (err,

stats) where stats is a fs.Stats object. fstat() is identical to stat(), except
that the file to be stat-ed is specified by the file descriptor fd.
fs.fstatSync(fd)#

fd <Integer>

Synchronous fstat(2). Returns an instance of fs.Stats.

fs.fsync(fd, callback)#

fd <Integer>

callback <Function>

Asynchronous fsync(2). No arguments other than a possible exception are

given to the completion callback.
fs.fsyncSync(fd)#

fd <Integer>

Synchronous fsync(2). Returns undefined.

fs.ftruncate(fd, len, callback)#

fd <Integer>

len <Integer>

callback <Function>

Asynchronous ftruncate(2). No arguments other than a possible exception

are given to the completion callback.
fs.ftruncateSync(fd, len)#

fd <Integer>

len <Integer>

Synchronous ftruncate(2). Returns undefined.

fs.futimes(fd, atime, mtime, callback)#

fd <Integer>

atime <Integer>

mtime <Integer>

callback <Function>

Change the file timestamps of a file referenced by the supplied file

descriptor.
fs.futimesSync(fd, atime, mtime)#

fd <Integer>

atime <Integer>

mtime <Integer>

Synchronous version of fs.futimes(). Returns undefined.

fs.lchmod(path, mode, callback)#

path <String> | <Buffer>

mode <Integer>

callback <Function>

Asynchronous lchmod(2). No arguments other than a possible exception

are given to the completion callback.
Only available on Mac OS X.
fs.lchmodSync(path, mode)#

path <String> | <Buffer>

mode <Integer>

Synchronous lchmod(2). Returns undefined.

fs.lchown(path, uid, gid, callback)#

path <String> | <Buffer>

uid <Integer>

gid <Integer>

callback <Function>

Asynchronous lchown(2). No arguments other than a possible exception

are given to the completion callback.
fs.lchownSync(path, uid, gid)#

path <String> | <Buffer>

uid <Integer>

gid <Integer>

Synchronous lchown(2). Returns undefined.

fs.link(srcpath, dstpath, callback)#

srcpath <String> | <Buffer>

dstpath <String> | <Buffer>

callback <Function>

Asynchronous link(2). No arguments other than a possible exception are

given to the completion callback.
fs.linkSync(srcpath, dstpath)#

srcpath <String> | <Buffer>

dstpath <String> | <Buffer>

Synchronous link(2). Returns undefined.

fs.lstat(path, callback)#

path <String> | <Buffer>

callback <Function>

Asynchronous lstat(2). The callback gets two arguments (err,

stats) where stats is a fs.Stats object. lstat() is identical to stat(), except
that ifpath is a symbolic link, then the link itself is stat-ed, not the file that
it refers to.
fs.lstatSync(path)#

path <String> | <Buffer>

Synchronous lstat(2). Returns an instance of fs.Stats.

fs.mkdir(path[, mode], callback)#

path <String> | <Buffer>

mode <Integer>

callback <Function>

Asynchronous mkdir(2). No arguments other than a possible exception are

given to the completion callback. mode defaults to 0o777.
fs.mkdirSync(path[, mode])#

path <String> | <Buffer>

mode <Integer>

Synchronous mkdir(2). Returns undefined.

fs.mkdtemp(prefix, callback)#
Creates a unique temporary directory.
Generates six random characters to be appended behind a
required prefix to create a unique temporary directory.
The created folder path is passed as a string to the callback's second
parameter.
Example:
fs.mkdtemp('/tmp/foo-', (err, folder) => {
console.log(folder);
// Prints: /tmp/foo-itXde2
});
fs.mkdtempSync(template)#

The synchronous version of [fs.mkdtemp()][]. Returns the created folder

path.
fs.open(path, flags[, mode], callback)#

path <String> | <Buffer>

flags <String> | <Number>

mode <Integer>

callback <Function>

Asynchronous file open. See open(2). flags can be:

'r' - Open file for reading. An exception occurs if the file does not
exist.

'r+' - Open file for reading and writing. An exception occurs if the file
does not exist.

'rs+' - Open file for reading and writing in synchronous mode.

Instructs the operating system to bypass the local file system cache.
This is primarily useful for opening files on NFS mounts as it allows
you to skip the potentially stale local cache. It has a very real impact
on I/O performance so don't use this flag unless you need it.
Note that this doesn't turn fs.open() into a synchronous blocking call.
If that's what you want then you should be using fs.openSync()

'w' - Open file for writing. The file is created (if it does not exist) or
truncated (if it exists).

'wx' - Like 'w' but fails if path exists.

'w+' - Open file for reading and writing. The file is created (if it does
not exist) or truncated (if it exists).

'wx+' - Like 'w+' but fails if path exists.

'a' - Open file for appending. The file is created if it does not exist.

'ax' - Like 'a' but fails if path exists.

'a+' - Open file for reading and appending. The file is created if it
does not exist.

'ax+' - Like 'a+' but fails if path exists.

mode sets the file mode (permission and sticky bits), but only if the file
was created. It defaults to 0666, readable and writable.
The callback gets two arguments (err, fd).
The exclusive flag 'x' (O_EXCL flag in open(2)) ensures that path is newly
created. On POSIX systems, path is considered to exist even if it is a
symlink to a non-existent file. The exclusive flag may or may not work
with network file systems.
flags can also be a number as documented by open(2); commonly used
constants are available from require('constants'). On Windows, flags are
translated to their equivalent ones where applicable,
e.g. O_WRONLY to FILE_GENERIC_WRITE, or O_EXCL|
O_CREAT to CREATE_NEW, as accepted by CreateFileW.
On Linux, positional writes don't work when the file is opened in append
mode. The kernel ignores the position argument and always appends the
data to the end of the file.
Note: The behavior of fs.open() is platform specific for some flags. As
such, opening a directory on OS X and Linux with the 'a+' flag - see
example below - will return an error. In contrast, on Windows and
FreeBSD, a file descriptor will be returned.
// OS X and Linux
fs.open('<directory>', 'a+', (err, fd) => {
// => [Error: EISDIR: illegal operation on a directory, open
<directory>]
})
// Windows and FreeBSD
fs.open('<directory>', 'a+', (err, fd) => {

// => null, <fd>

})
fs.openSync(path, flags[, mode])#

path <String> | <Buffer>

flags <String> | <Number>

mode <Integer>

Synchronous version of fs.open(). Returns an integer representing the file

descriptor.
fs.read(fd, buffer, offset, length, position, callback)#

fd <Integer>

buffer <String> | <Buffer>

offset <Integer>

length <Integer>

position <Integer>

callback <Function>

Read data from the file specified by fd.

buffer is the buffer that the data will be written to.
offset is the offset in the buffer to start writing at.
length is an integer specifying the number of bytes to read.
position is an integer specifying where to begin reading from in the file.
If position is null, data will be read from the current file position.
The callback is given the three arguments, (err, bytesRead, buffer).
fs.readdir(path[, options], callback)#

path <String> | <Buffer>

options <String> | <Object>

o

encoding <String> default = 'utf8'

callback <Function>

Asynchronous readdir(3). Reads the contents of a directory. The callback

gets two arguments (err, files) where files is an array of the names of the
files in the directory excluding '.' and '..'.
The optional options argument can be a string specifying an encoding, or
an object with an encoding property specifying the character encoding to
use for the filenames passed to the callback. If the encoding is set
to 'buffer', the filenames returned will be passed as Buffer objects.
fs.readdirSync(path[, options])#

path <String> | <Buffer>

options <String> | <Object>

o

encoding <String> default = 'utf8'

Synchronous readdir(3). Returns an array of filenames excluding '.' and '..'.

The optional options argument can be a string specifying an encoding, or
an object with an encoding property specifying the character encoding to
use for the filenames passed to the callback. If the encoding is set
to 'buffer', the filenames returned will be passed as Buffer objects.
fs.readFile(file[, options], callback)#

file <String> | <Buffer> | <Integer> filename or file descriptor

options <Object> | <String>

encoding <String> | <Null> default = null

flag <String> default = 'r'

callback <Function>

Asynchronously reads the entire contents of a file. Example:

fs.readFile('/etc/passwd', (err, data) => {

if (err) throw err;
console.log(data);
});
The callback is passed two arguments (err, data), where data is the
contents of the file.
If no encoding is specified, then the raw buffer is returned.
If options is a string, then it specifies the encoding. Example:
fs.readFile('/etc/passwd', 'utf8', callback);
Any specified file descriptor has to support reading.
Note: Specified file descriptors will not be closed automatically.
fs.readFileSync(file[, options])#

file <String> | <Buffer> | <Integer> filename or file descriptor

options <Object> | <String>

o

encoding <String> | <Null> default = null

flag <String> default = 'r'

Synchronous version of fs.readFile. Returns the contents of the file.

If the encoding option is specified then this function returns a string.
Otherwise it returns a buffer.
fs.readlink(path[, options], callback)#

path <String> | <Buffer>

options <String> | <Object>

o

encoding <String> default = 'utf8'

callback <Function>

Asynchronous readlink(2). The callback gets two arguments (err,

linkString).
The optional options argument can be a string specifying an encoding, or
an object with an encoding property specifying the character encoding to
use for the link path passed to the callback. If the encoding is set
to 'buffer', the link path returned will be passed as a Buffer object.
fs.readlinkSync(path[, options])#

path <String> | <Buffer>

options <String> | <Object>

o

encoding <String> default = 'utf8'

Synchronous readlink(2). Returns the symbolic link's string value.

The optional options argument can be a string specifying an encoding, or
an object with an encoding property specifying the character encoding to
use for the link path passed to the callback. If the encoding is set
to 'buffer', the link path returned will be passed as a Buffer object.
fs.readSync(fd, buffer, offset, length, position)#

fd <Integer>

buffer <String> | <Buffer>

offset <Integer>

length <Integer>

position <Integer>

Synchronous version of fs.read(). Returns the number of bytesRead.

fs.realpath(path[, options], callback)#

path <String> | <Buffer>

options <String> | <Object>

o

encoding <String> default = 'utf8'

callback <Function>

Asynchronous realpath(3). The callback gets two arguments (err,

resolvedPath). May use process.cwd to resolve relative paths.
The optional options argument can be a string specifying an encoding, or
an object with an encoding property specifying the character encoding to
use for the path passed to the callback. If the encoding is set to 'buffer',
the path returned will be passed as a Buffer object.
fs.realpathSync(path[, options])#

path <String> | <Buffer>;

options <String> | <Object>

o

encoding <String> default = 'utf8'

Synchronous realpath(3). Returns the resolved path.

The optional options argument can be a string specifying an encoding, or
an object with an encoding property specifying the character encoding to
use for the path passed to the callback. If the encoding is set to 'buffer',
the path returned will be passed as a Buffer object.
fs.rename(oldPath, newPath, callback)#

oldPath <String> | <Buffer>

newPath <String> | <Buffer>

callback <Function>

Asynchronous rename(2). No arguments other than a possible exception

are given to the completion callback.
fs.renameSync(oldPath, newPath)#

oldPath <String> | <Buffer>

newPath <String> | <Buffer>

Synchronous rename(2). Returns undefined.

fs.rmdir(path, callback)#

path <String> | <Buffer>

callback <Function>

Asynchronous rmdir(2). No arguments other than a possible exception are

given to the completion callback.
fs.rmdirSync(path)#

path <String> | <Buffer>

Synchronous rmdir(2). Returns undefined.

fs.stat(path, callback)#

path <String> | <Buffer>

callback <Function>

Asynchronous stat(2). The callback gets two arguments (err,

stats) where stats is a fs.Stats object. See the fs.Stats section for more
information.
fs.statSync(path)#

path <String> | <Buffer>

Synchronous stat(2). Returns an instance of fs.Stats.

fs.symlink(target, path[, type], callback)#

target <String> | <Buffer>

path <String> | <Buffer>

type <String>

callback <Function>

Asynchronous symlink(2). No arguments other than a possible exception

are given to the completion callback. The type argument can be set
to 'dir','file', or 'junction' (default is 'file') and is only available on Windows

(ignored on other platforms). Note that Windows junction points require

the destination path to be absolute. When using 'junction',
the target argument will automatically be normalized to absolute path.
Here is an example below:
fs.symlink('./foo', './new-port');
It creates a symbolic link named "new-port" that points to "foo".
fs.symlinkSync(target, path[, type])#

target <String> | <Buffer>

path <String> | <Buffer>

type <String>

Synchronous symlink(2). Returns undefined.

fs.truncate(path, len, callback)#

path <String> | <Buffer>

len <Integer>

callback <Function>

Asynchronous truncate(2). No arguments other than a possible exception

are given to the completion callback. A file descriptor can also be passed
as the first argument. In this case, fs.ftruncate() is called.
fs.truncateSync(path, len)#

path <String> | <Buffer>

len <Integer>

Synchronous truncate(2). Returns undefined.

fs.unlink(path, callback)#

path <String> | <Buffer>

callback <Function>

Asynchronous unlink(2). No arguments other than a possible exception are

given to the completion callback.
fs.unlinkSync(path)#

path <String> | <Buffer>

Synchronous unlink(2). Returns undefined.

fs.unwatchFile(filename[, listener])#

filename <String> | <Buffer>

listener <Function>

Stop watching for changes on filename. If listener is specified, only that

particular listener is removed. Otherwise, all listeners are removed and
you have effectively stopped watching filename.
Calling fs.unwatchFile() with a filename that is not being watched is a noop, not an error.
Note: fs.watch() is more efficient
than fs.watchFile() and fs.unwatchFile(). fs.watch() should be used instead
of fs.watchFile() andfs.unwatchFile() when possible.
fs.utimes(path, atime, mtime, callback)#

path <String> | <Buffer>

atime <Integer>

mtime <Integer>

callback <Function>

Change file timestamps of the file referenced by the supplied path.

Note: the arguments atime and mtime of the following related functions
does follow the below rules:

If the value is a numberable string like '123456789', the value would

get converted to corresponding number.

If the value is NaN or Infinity, the value would get converted

to Date.now().

fs.utimesSync(path, atime, mtime)#

path <String> | <Buffer>

atime <Integer>

mtime <Integer>

Synchronous version of fs.utimes(). Returns undefined.

fs.watch(filename[, options][, listener])#

filename <String> | <Buffer>

options <String> | <Object>

persistent <Boolean> Indicates whether the process should

continue to run as long as files are being watched. default = true

recursive <Boolean> Indicates whether all subdirectories

should be watched, or only the current directory. The applies when
a directory is specified, and only on supported platforms
(See Caveats). default = false

encoding <String> Specifies the character encoding to be

used for the filename passed to the listener. default = 'utf8'

listener <Function>

Watch for changes on filename, where filename is either a file or a

directory. The returned object is a fs.FSWatcher.
The second argument is optional. If options is provided as a string, it
specifies the encoding. Otherwise options should be passed as an object.
The listener callback gets two arguments (event, filename). event is
either 'rename' or 'change', and filename is the name of the file which
triggered the event.

Caveats#
The fs.watch API is not 100% consistent across platforms, and is
unavailable in some situations.
The recursive option is only supported on OS X and Windows.
Availability#

This feature depends on the underlying operating system providing a way

to be notified of filesystem changes.

On Linux systems, this uses inotify.

On BSD systems, this uses kqueue.

On OS X, this uses kqueue for files and 'FSEvents' for directories.

On SunOS systems (including Solaris and SmartOS), this uses event

ports.

On Windows systems, this feature depends

on ReadDirectoryChangesW.

If the underlying functionality is not available for some reason,

then fs.watch will not be able to function. For example, watching files or
directories on network file systems (NFS, SMB, etc.) often doesn't work
reliably or at all.
You can still use fs.watchFile, which uses stat polling, but it is slower and
less reliable.
Inodes#

On Linux and OS X systems, fs.watch() resolves the path to an inode and

watches the inode. If the watched path is deleted and recreated, it is
assigned a new inode. The watch will emit an event for the delete but will
continue watching the original inode. Events for the new inode will not be
emitted. This is expected behavior.
Filename Argument#

Providing filename argument in the callback is only supported on Linux

and Windows. Even on supported platforms, filename is not always
guaranteed to be provided. Therefore, don't assume
that filename argument is always provided in the callback, and have some
fallback logic if it is null.
fs.watch('somedir', (event, filename) => {
console.log(`event is: ${event}`);
if (filename) {
console.log(`filename provided: ${filename}`);
} else {
console.log('filename not provided');
}
});
fs.watchFile(filename[, options], listener)#

filename <String> | <Buffer>

options <Object>

persistent <Boolean>

interval <Integer>

listener <Function>

Watch for changes on filename. The callback listener will be called each
time the file is accessed.
The options argument may be omitted. If provided, it should be an object.
The options object may contain a boolean named persistent that indicates
whether the process should continue to run as long as files are being
watched. The options object may specify an interval property indicating
how often the target should be polled in milliseconds. The default
is { persistent: true, interval: 5007 }.
The listener gets two arguments the current stat object and the previous
stat object:
fs.watchFile('message.text', (curr, prev) => {
console.log(`the current mtime is: ${curr.mtime}`);

console.log(`the previous mtime was: ${prev.mtime}`);

});
These stat objects are instances of fs.Stat.
If you want to be notified when the file was modified, not just accessed,
you need to compare curr.mtime and prev.mtime.
Note: when an fs.watchFile operation results in an ENOENT error, it will
invoke the listener once, with all the fields zeroed (or, for dates, the Unix
Epoch). In Windows, blksize and blocks fields will be undefined, instead of
zero. If the file is created later on, the listener will be called again, with
the latest stat objects. This is a change in functionality since v0.10.
Note: fs.watch() is more efficient
than fs.watchFile and fs.unwatchFile. fs.watch should be used instead
of fs.watchFile and fs.unwatchFile when possible.
fs.write(fd, buffer, offset, length[, position], callback)#

fd <Integer>

buffer <String> | <Buffer>

offset <Integer>

length <Integer>

position <Integer>

callback <Function>

Write buffer to the file specified by fd.

offset and length determine the part of the buffer to be written.
position refers to the offset from the beginning of the file where this data
should be written. If typeof position !== 'number', the data will be written
at the current position. See pwrite(2).
The callback will be given three arguments (err, written,
buffer) where written specifies how many bytes were written from buffer.

Note that it is unsafe to use fs.write multiple times on the same file
without waiting for the callback. For this scenario, fs.createWriteStream is
strongly recommended.
On Linux, positional writes don't work when the file is opened in append
mode. The kernel ignores the position argument and always appends the
data to the end of the file.
fs.write(fd, data[, position[, encoding]], callback)#

fd <Integer>

data <String> | <Buffer>

position <Integer>

encoding <String>

callback <Function>

Write data to the file specified by fd. If data is not a Buffer instance then
the value will be coerced to a string.
position refers to the offset from the beginning of the file where this data
should be written. If typeof position !== 'number' the data will be written
at the current position. See pwrite(2).
encoding is the expected string encoding.
The callback will receive the arguments (err, written,
string) where written specifies how many bytes the passed string required
to be written. Note that bytes written is not the same as string characters.
See Buffer.byteLength.
Unlike when writing buffer, the entire string must be written. No substring
may be specified. This is because the byte offset of the resulting data may
not be the same as the string offset.
Note that it is unsafe to use fs.write multiple times on the same file
without waiting for the callback. For this scenario, fs.createWriteStream is
strongly recommended.

On Linux, positional writes don't work when the file is opened in append
mode. The kernel ignores the position argument and always appends the
data to the end of the file.
fs.writeFile(file, data[, options], callback)#

file <String> | <Buffer> | <Integer> filename or file descriptor

data <String> | <Buffer>

options <Object> | <String>

encoding <String> | <Null> default = 'utf8'

mode <Integer> default = 0o666

flag <String> default = 'w'

callback <Function>

Asynchronously writes data to a file, replacing the file if it already

exists. data can be a string or a buffer.
The encoding option is ignored if data is a buffer. It defaults to 'utf8'.
Example:
fs.writeFile('message.txt', 'Hello Node.js', (err) => {
if (err) throw err;
console.log('It\'s saved!');
});
If options is a string, then it specifies the encoding. Example:
fs.writeFile('message.txt', 'Hello Node.js', 'utf8', callback);
Any specified file descriptor has to support writing.
Note that it is unsafe to use fs.writeFile multiple times on the same file
without waiting for the callback. For this scenario, fs.createWriteStream is
strongly recommended.
Note: Specified file descriptors will not be closed automatically.

fs.writeFileSync(file, data[, options])#

file <String> | <Buffer> | <Integer> filename or file descriptor

data <String> | <Buffer>

options <Object> | <String>

o

encoding <String> | <Null> default = 'utf8'

mode <Integer> default = 0o666

flag <String> default = 'w'

The synchronous version of fs.writeFile(). Returns undefined.

fs.writeSync(fd, buffer, offset, length[, position])#

fd <Integer>

buffer <String> | <Buffer>

offset <Integer>

length <Integer>

position <Integer>

fs.writeSync(fd, data[, position[, encoding]])#

fd <Integer>

data <String> | <Buffer>

position <Integer>

encoding <String>

Synchronous versions of fs.write(). Returns the number of bytes written.

Global Objects#
These objects are available in all modules. Some of these objects aren't
actually in the global scope but in the module scope - this will be noted.

Class: Buffer#

<Function>

Used to handle binary data. See the buffer section.

__dirname#

<String>

The name of the directory that the currently executing script resides in.
Example: running node example.js from /Users/mjr
console.log(__dirname);
// /Users/mjr
__dirname isn't actually a global but rather local to each module.
For instance, given two modules: a and b, where b is a dependency
of a and there is a directory structure of:

/Users/mjr/app/a.js

/Users/mjr/app/node_modules/b/b.js

References to __dirname within b.js will

return /Users/mjr/app/node_modules/b while references
to __dirname within a.js will return/Users/mjr/app.
__filename#

<String>

The filename of the code being executed. This is the resolved absolute
path of this code file. For a main program this is not necessarily the same
filename used in the command line. The value inside a module is the path
to that module file.
Example: running node example.js from /Users/mjr
console.log(__filename);
// /Users/mjr/example.js

__filename isn't actually a global but rather local to each module.

clearImmediate(immediateObject)#
clearImmediate is described in the timers section.
clearInterval(intervalObject)#
clearInterval is described in the timers section.
clearTimeout(timeoutObject)#
clearTimeout is described in the timers section.
console#

<Object>

Used to print to stdout and stderr. See the console section.

exports#
A reference to the module.exports that is shorter to type. See module
system documentation for details on when to use exports and when to
usemodule.exports.
exports isn't actually a global but rather local to each module.
See the module system documentation for more information.
global#

<Object> The global namespace object.

In browsers, the top-level scope is the global scope. That means that in
browsers if you're in the global scope var something will define a global
variable. In Node.js this is different. The top-level scope is not the global
scope; var something inside an Node.js module will be local to that
module.
module#

<Object>

A reference to the current module. In particular module.exports is used for

defining what a module exports and makes available through require().
module isn't actually a global but rather local to each module.
See the module system documentation for more information.
process#

<Object>

The process object. See the process object section.

require()#

<Function>

To require modules. See the Modules section. require isn't actually a global
but rather local to each module.
require.cache#

<Object>

Modules are cached in this object when they are required. By deleting a
key value from this object, the next require will reload the module. Note
that this does not apply to native addons, for which reloading will result in
an Error.
require.extensions#
Stability: 0 - Deprecated

<Object>

Instruct require on how to handle certain file extensions.

Process files with the extension .sjs as .js:
require.extensions['.sjs'] = require.extensions['.js'];
Deprecated In the past, this list has been used to load non-JavaScript
modules into Node.js by compiling them on-demand. However, in practice,

there are much better ways to do this, such as loading modules via some
other Node.js program, or compiling them to JavaScript ahead of time.
Since the Module system is locked, this feature will probably never go
away. However, it may have subtle bugs and complexities that are best
left untouched.
require.resolve()#
Use the internal require() machinery to look up the location of a module,
but rather than loading the module, just return the resolved filename.
setImmediate(callback[, arg][, ...])#
setImmediate is described in the timers section.
setInterval(callback, delay[, arg][, ...])#
setInterval is described in the timers section.
setTimeout(callback, delay[, arg][, ...])#
setTimeout is described in the timers section.

HTTP#
Stability: 2 - Stable
To use the HTTP server and client one must require('http').
The HTTP interfaces in Node.js are designed to support many features of
the protocol which have been traditionally difficult to use. In particular,
large, possibly chunk-encoded, messages. The interface is careful to never
buffer entire requests or responses--the user is able to stream data.
HTTP message headers are represented by an object like this:
{ 'content-length': '123',
'content-type': 'text/plain',
'connection': 'keep-alive',
'host': 'mysite.com',

'accept': '*/*' }
Keys are lowercased. Values are not modified.
In order to support the full spectrum of possible HTTP applications,
Node.js's HTTP API is very low-level. It deals with stream handling and
message parsing only. It parses a message into headers and body but it
does not parse the actual headers or the body.
See message.headers for details on how duplicate headers are handled.
The raw headers as they were received are retained in
the rawHeaders property, which is an array of [key, value, key2,
value2, ...]. For example, the previous message header object might have
a rawHeaders list like the following:
[ 'ConTent-Length', '123456',
'content-LENGTH', '123',
'content-type', 'text/plain',
'CONNECTION', 'keep-alive',
'Host', 'mysite.com',
'accepT', '*/*' ]
Class: http.Agent#
The HTTP Agent is used for pooling sockets used in HTTP client requests.
The HTTP Agent also defaults client requests to using Connection:keepalive. If no pending HTTP requests are waiting on a socket to become free
the socket is closed. This means that Node.js's pool has the benefit of
keep-alive when under load but still does not require developers to
manually close the HTTP clients using KeepAlive.
If you opt into using HTTP KeepAlive, you can create an Agent object with
that flag set to true. (See the constructor options.) Then, the Agent will
keep unused sockets in a pool for later use. They will be explicitly marked
so as to not keep the Node.js process running. However, it is still a good
idea to explicitly destroy() KeepAlive agents when they are no longer in
use, so that the Sockets will be shut down.

Sockets are removed from the agent's pool when the socket emits either
a 'close' event or a special 'agentRemove' event. This means that if you
intend to keep one HTTP request open for a long time and don't want it to
stay in the pool you can do something along the lines of:
http.get(options, (res) => {
// Do stuff
}).on('socket', (socket) => {
socket.emit('agentRemove');
});
Alternatively, you could just opt out of pooling entirely using agent:false:
http.get({
hostname: 'localhost',
port: 80,
path: '/',
agent: false // create a new agent just for this one request
}, (res) => {
// Do stuff with response
})
new Agent([options])#

options <Object> Set of configurable options to set on the agent.

Can have the following fields:
o

keepAlive <Boolean> Keep sockets around in a pool to be

used by other requests in the future. Default = false

keepAliveMsecs <Integer> When using HTTP KeepAlive, how

often to send TCP KeepAlive packets over sockets being kept alive.
Default =1000. Only relevant if keepAlive is set to true.

maxSockets <Number> Maximum number of sockets to allow

per host. Default = Infinity.

maxFreeSockets <Number> Maximum number of sockets to

leave open in a free state. Only relevant if keepAlive is set to true.
Default = 256.

The default http.globalAgent that is used by http.request() has all of these

values set to their respective defaults.

To configure any of them, you must create your own http.Agent object.
const http = require('http');
var keepAliveAgent = new http.Agent({ keepAlive: true });
options.agent = keepAliveAgent;
http.request(options, onResponseCallback);
agent.createConnection(options[, callback])#
Produces a socket/stream to be used for HTTP requests.
By default, this function is the same as net.createConnection(). However,
custom Agents may override this method in case greater flexibility is
desired.
A socket/stream can be supplied in one of two ways: by returning the
socket/stream from this function, or by passing the socket/stream
to callback.
callback has a signature of (err, stream).
agent.destroy()#
Destroy any sockets that are currently in use by the agent.
It is usually not necessary to do this. However, if you are using an agent
with KeepAlive enabled, then it is best to explicitly shut down the agent
when you know that it will no longer be used. Otherwise, sockets may
hang open for quite a long time before the server terminates them.
agent.freeSockets#
An object which contains arrays of sockets currently awaiting use by the
Agent when HTTP KeepAlive is used. Do not modify.
agent.getName(options)#
Get a unique name for a set of request options, to determine whether a
connection can be reused. In the http agent, this
returns host:port:localAddress. In the https agent, the name includes the
CA, cert, ciphers, and other HTTPS/TLS-specific options that determine
socket reusability.

Options:

host: A domain name or IP address of the server to issue the request

to.
port: Port of remote server.

localAddress: Local interface to bind for network connections when

issuing the request.
agent.maxFreeSockets#
By default set to 256. For Agents supporting HTTP KeepAlive, this sets the
maximum number of sockets that will be left open in the free state.
agent.maxSockets#
By default set to Infinity. Determines how many concurrent sockets the
agent can have open per origin. Origin is either a 'host:port' or
'host:port:localAddress' combination.
agent.requests#
An object which contains queues of requests that have not yet been
assigned to sockets. Do not modify.
agent.sockets#
An object which contains arrays of sockets currently in use by the Agent.
Do not modify.
Class: http.ClientRequest#
This object is created internally and returned from http.request(). It
represents an in-progress request whose header has already been
queued. The header is still mutable using the setHeader(name,
value), getHeader(name), removeHeader(name) API. The actual header
will be sent along with the first data chunk or when closing the
connection.
To get the response, add a listener for 'response' to the request
object. 'response' will be emitted from the request object when the
response headers have been received. The 'response' event is executed
with one argument which is an instance of http.IncomingMessage.

During the 'response' event, one can add listeners to the response object;
particularly to listen for the 'data' event.
If no 'response' handler is added, then the response will be entirely
discarded. However, if you add a 'response' event handler, then
you must consume the data from the response object, either by
calling response.read() whenever there is a 'readable' event, or by adding
a 'data' handler, or by calling the .resume() method. Until the data is
consumed, the 'end' event will not fire. Also, until the data is read it will
consume memory that can eventually lead to a 'process out of memory'
error.
Note: Node.js does not check whether Content-Length and the length of
the body which has been transmitted are equal or not.
The request implements the Writable Stream interface. This is
an EventEmitter with the following events:
Event: 'abort'#
function () { }
Emitted when the request has been aborted by the client. This event is
only emitted on the first call to abort().
Event: 'checkExpectation'#
function (request, response) { }
Emitted each time a request with an http Expect header is received,
where the value is not 100-continue. If this event isn't listened for, the
server will automatically respond with a 417 Expectation Failed as
appropriate.
Note that when this event is emitted and handled, the request event will
not be emitted.
Event: 'connect'#
function (response, socket, head) { }

Emitted each time a server responds to a request with

a CONNECT method. If this event isn't being listened for, clients receiving
a CONNECT method will have their connections closed.
A client server pair that show you how to listen for the 'connect' event.
const http = require('http');
const net = require('net');
const url = require('url');
// Create an HTTP tunneling proxy
var proxy = http.createServer( (req, res) => {
res.writeHead(200, {'Content-Type': 'text/plain'});
res.end('okay');
});
proxy.on('connect', (req, cltSocket, head) => {
// connect to an origin server
var srvUrl = url.parse(`http://${req.url}`);
var srvSocket = net.connect(srvUrl.port, srvUrl.hostname, () => {
cltSocket.write('HTTP/1.1 200 Connection Established\r\n' +
'Proxy-agent: Node.js-Proxy\r\n' +
'\r\n');
srvSocket.write(head);
srvSocket.pipe(cltSocket);
cltSocket.pipe(srvSocket);
});
});
// now that proxy is running
proxy.listen(1337, '127.0.0.1', () => {
// make a request to a tunneling proxy
var options = {
port: 1337,
hostname: '127.0.0.1',
method: 'CONNECT',
path: 'www.google.com:80'
};

var req = http.request(options);

req.end();
req.on('connect', (res, socket, head) => {
console.log('got connected!');
// make a request over an HTTP tunnel
socket.write('GET / HTTP/1.1\r\n' +
'Host: www.google.com:80\r\n' +
'Connection: close\r\n' +
'\r\n');
socket.on('data', (chunk) => {
console.log(chunk.toString());
});
socket.on('end', () => {
proxy.close();
});
});
});
Event: 'continue'#
function () { }
Emitted when the server sends a '100 Continue' HTTP response, usually
because the request contained 'Expect: 100-continue'. This is an
instruction that the client should send the request body.
Event: 'response'#
function (response) { }
Emitted when a response is received to this request. This event is emitted
only once. The response argument will be an instance
ofhttp.IncomingMessage.
Event: 'socket'#
function (socket) { }
Emitted after a socket is assigned to this request.

Event: 'upgrade'#
function (response, socket, head) { }
Emitted each time a server responds to a request with an upgrade. If this
event isn't being listened for, clients receiving an upgrade header will
have their connections closed.
A client server pair that show you how to listen for the 'upgrade' event.
const http = require('http');
// Create an HTTP server
var srv = http.createServer( (req, res) => {
res.writeHead(200, {'Content-Type': 'text/plain'});
res.end('okay');
});
srv.on('upgrade', (req, socket, head) => {
socket.write('HTTP/1.1 101 Web Socket Protocol Handshake\r\n' +
'Upgrade: WebSocket\r\n' +
'Connection: Upgrade\r\n' +
'\r\n');
socket.pipe(socket); // echo back
});
// now that server is running
srv.listen(1337, '127.0.0.1', () => {
// make a request
var options = {
port: 1337,
hostname: '127.0.0.1',
headers: {
'Connection': 'Upgrade',
'Upgrade': 'websocket'
}
};

var req = http.request(options);

req.end();
req.on('upgrade', (res, socket, upgradeHead) => {
console.log('got upgraded!');
socket.end();
process.exit(0);
});
});
request.abort()#
Marks the request as aborting. Calling this will cause remaining data in the
response to be dropped and the socket to be destroyed.
request.end([data][, encoding][, callback])#
Finishes sending the request. If any parts of the body are unsent, it will
flush them to the stream. If the request is chunked, this will send the
terminating'0\r\n\r\n'.
If data is specified, it is equivalent to calling response.write(data,
encoding) followed by request.end(callback).
If callback is specified, it will be called when the request stream is
finished.
request.flushHeaders()#
Flush the request headers.
For efficiency reasons, Node.js normally buffers the request headers until
you call request.end() or write the first chunk of request data. It then tries
hard to pack the request headers and data into a single TCP packet.
That's usually what you want (it saves a TCP round-trip) but not when the
first data isn't sent until possibly much later. request.flushHeaders() lets
you bypass the optimization and kickstart the request.

request.setNoDelay([noDelay])#
Once a socket is assigned to this request and is
connected socket.setNoDelay() will be called.
request.setSocketKeepAlive([enable][, initialDelay])#
Once a socket is assigned to this request and is
connected socket.setKeepAlive() will be called.
request.setTimeout(timeout[, callback])#
Once a socket is assigned to this request and is
connected socket.setTimeout() will be called.

timeout <Number> Milliseconds before a request is considered to

be timed out.

callback <Function> Optional function to be called when a timeout

occurs. Same as binding to the timeout event.
request.write(chunk[, encoding][, callback])#
Sends a chunk of the body. By calling this method many times, the user
can stream a request body to a server--in that case it is suggested to use
the['Transfer-Encoding', 'chunked'] header line when creating the request.
The chunk argument should be a Buffer or a string.
The encoding argument is optional and only applies when chunk is a
string. Defaults to 'utf8'.
The callback argument is optional and will be called when this chunk of
data is flushed.
Returns request.
Class: http.Server#
This class inherits from net.Server and has the following additional events:
Event: 'checkContinue'#
function (request, response) { }

Emitted each time a request with an http Expect: 100-continue is

received. If this event isn't listened for, the server will automatically
respond with a 100 Continue as appropriate.
Handling this event involves calling response.writeContinue() if the client
should continue to send the request body, or generating an appropriate
HTTP response (e.g., 400 Bad Request) if the client should not continue to
send the request body.
Note that when this event is emitted and handled, the 'request' event will
not be emitted.
Event: 'clientError'#
function (exception, socket) { }
If a client connection emits an 'error' event, it will be forwarded here.
Listener of this event is responsible for closing/destroying the underlying
socket. For example, one may wish to more gracefully close the socket
with an HTTP '400 Bad Request' response instead of abruptly severing the
connection.
Default behavior is to destroy the socket immediately on malformed
request.
socket is the net.Socket object that the error originated from.
const http = require('http');
const server = http.createServer((req, res) => {
res.end();
});
server.on('clientError', (err, socket) => {
socket.end('HTTP/1.1 400 Bad Request\r\n\r\n');
});
server.listen(8000);
When the 'clientError' event occurs, there is
no request or response object, so any HTTP response sent, including
response headers and payload,must be written directly to

the socket object. Care must be taken to ensure the response is a properly
formatted HTTP response message.
Event: 'close'#
function () { }
Emitted when the server closes.
Event: 'connect'#
function (request, socket, head) { }
Emitted each time a client requests a http CONNECT method. If this event
isn't listened for, then clients requesting a CONNECT method will have
their connections closed.

request is the arguments for the http request, as it is in the request

event.

socket is the network socket between the server and client.

head is an instance of Buffer, the first packet of the tunneling

stream, this may be empty.

After this event is emitted, the request's socket will not have
a 'data' event listener, meaning you will need to bind to it in order to
handle data sent to the server on that socket.
Event: 'connection'#
function (socket) { }
When a new TCP stream is established. socket is an object of
type net.Socket. Usually users will not want to access this event. In
particular, the socket will not emit 'readable' events because of how the
protocol parser attaches to the socket. The socket can also be accessed
at request.connection.
Event: 'request'#
function (request, response) { }

Emitted each time there is a request. Note that there may be multiple
requests per connection (in the case of keep-alive connections). request is
an instance of http.IncomingMessage and response is an instance
of http.ServerResponse.
Event: 'upgrade'#
function (request, socket, head) { }
Emitted each time a client requests a http upgrade. If this event isn't
listened for, then clients requesting an upgrade will have their
connections closed.

request is the arguments for the http request, as it is in the request

event.

socket is the network socket between the server and client.

head is an instance of Buffer, the first packet of the upgraded

stream, this may be empty.

After this event is emitted, the request's socket will not have
a 'data' event listener, meaning you will need to bind to it in order to
handle data sent to the server on that socket.
server.close([callback])#
Stops the server from accepting new connections. See net.Server.close().
server.listen(handle[, callback])#

handle <Object>

callback <Function>

The handle object can be set to either a server or socket (anything with an
underlying _handle member), or a {fd: <n>} object.
This will cause the server to accept connections on the specified handle,
but it is presumed that the file descriptor or handle has already been
bound to a port or domain socket.
Listening on a file descriptor is not supported on Windows.

This function is asynchronous. The last parameter callback will be added

as a listener for the 'listening' event. See also net.Server.listen().
Returns server.
server.listen(path[, callback])#
Start a UNIX socket server listening for connections on the given path.
This function is asynchronous. The last parameter callback will be added
as a listener for the 'listening' event. See also net.Server.listen(path).
server.listen(port[, hostname][, backlog][, callback])#
Begin accepting connections on the specified port and hostname. If
the hostname is omitted, the server will accept connections on any IPv6
address (::) when IPv6 is available, or any IPv4 address (0.0.0.0)
otherwise. A port value of zero will assign a random port.
To listen to a unix socket, supply a filename instead of port and hostname.
Backlog is the maximum length of the queue of pending connections. The
actual length will be determined by your OS through sysctl settings such
astcp_max_syn_backlog and somaxconn on linux. The default value of this
parameter is 511 (not 512).
This function is asynchronous. The last parameter callback will be added
as a listener for the 'listening' event. See also net.Server.listen(port).
server.listening#
A Boolean indicating whether or not the server is listening for connections.
server.maxHeadersCount#
Limits maximum incoming headers count, equal to 1000 by default. If set
to 0 - no limit will be applied.
server.setTimeout(msecs, callback)#

msecs <Number>

callback <Function>

Sets the timeout value for sockets, and emits a 'timeout' event on the
Server object, passing the socket as an argument, if a timeout occurs.
If there is a 'timeout' event listener on the Server object, then it will be
called with the timed-out socket as an argument.
By default, the Server's timeout value is 2 minutes, and sockets are
destroyed automatically if they time out. However, if you assign a callback
to the Server's 'timeout' event, then you are responsible for handling
socket timeouts.
Returns server.
server.timeout#

<Number> Default = 120000 (2 minutes)

The number of milliseconds of inactivity before a socket is presumed to

have timed out.
Note that the socket timeout logic is set up on connection, so changing
this value only affects new connections to the server, not any existing
connections.
Set to 0 to disable any kind of automatic timeout behavior on incoming
connections.
Class: http.ServerResponse#
This object is created internally by a HTTP server--not by the user. It is
passed as the second parameter to the 'request' event.
The response implements, but does not inherit from, the Writable
Stream interface. This is an EventEmitter with the following events:
Event: 'close'#
function () { }
Indicates that the underlying connection was terminated
before response.end() was called or able to flush.

Event: 'finish'#
function () { }
Emitted when the response has been sent. More specifically, this event is
emitted when the last segment of the response headers and body have
been handed off to the operating system for transmission over the
network. It does not imply that the client has received anything yet.
After this event, no more events will be emitted on the response object.
response.addTrailers(headers)#
This method adds HTTP trailing headers (a header but at the end of the
message) to the response.
Trailers will only be emitted if chunked encoding is used for the response;
if it is not (e.g., if the request was HTTP/1.0), they will be silently
discarded.
Note that HTTP requires the Trailer header to be sent if you intend to emit
trailers, with a list of the header fields in its value. E.g.,
response.writeHead(200, { 'Content-Type': 'text/plain',
'Trailer': 'Content-MD5' });
response.write(fileData);
response.addTrailers({'Content-MD5':
'7895bf4b8828b55ceaf47747b4bca667'});
response.end();
Attempting to set a header field name or value that contains invalid
characters will result in a TypeError being thrown.
response.end([data][, encoding][, callback])#
This method signals to the server that all of the response headers and
body have been sent; that server should consider this message complete.
The method, response.end(), MUST be called on each response.
If data is specified, it is equivalent to calling response.write(data,
encoding) followed by response.end(callback).

If callback is specified, it will be called when the response stream is

finished.
response.finished#
Boolean value that indicates whether the response has completed. Starts
as false. After response.end() executes, the value will be true.
response.getHeader(name)#
Reads out a header that's already been queued but not sent to the client.
Note that the name is case insensitive. This can only be called before
headers get implicitly flushed.
Example:
var contentType = response.getHeader('content-type');
response.headersSent#
Boolean (read-only). True if headers were sent, false otherwise.
response.removeHeader(name)#
Removes a header that's queued for implicit sending.
Example:
response.removeHeader('Content-Encoding');
response.sendDate#
When true, the Date header will be automatically generated and sent in
the response if it is not already present in the headers. Defaults to true.
This should only be disabled for testing; HTTP requires the Date header in
responses.
response.setHeader(name, value)#
Sets a single header value for implicit headers. If this header already
exists in the to-be-sent headers, its value will be replaced. Use an array of
strings here if you need to send multiple headers with the same name.

Example:
response.setHeader('Content-Type', 'text/html');
or
response.setHeader('Set-Cookie', ['type=ninja',
'language=javascript']);
Attempting to set a header field name or value that contains invalid
characters will result in a TypeError being thrown.
When headers have been set with response.setHeader(), they will be
merged with any headers passed to response.writeHead(), with the
headers passed to response.writeHead() given precedence.
// returns content-type = text/plain
const server = http.createServer((req,res) => {
res.setHeader('Content-Type', 'text/html');
res.setHeader('X-Foo', 'bar');
res.writeHead(200, {'Content-Type': 'text/plain'});
res.end('ok');
});
response.setTimeout(msecs, callback)#

msecs <Number>

callback <Function>

Sets the Socket's timeout value to msecs. If a callback is provided, then it

is added as a listener on the 'timeout' event on the response object.
If no 'timeout' listener is added to the request, the response, or the server,
then sockets are destroyed when they time out. If you assign a handler on
the request, the response, or the server's 'timeout' events, then it is your
responsibility to handle timed out sockets.
Returns response.

response.statusCode#
When using implicit headers (not calling response.writeHead() explicitly),
this property controls the status code that will be sent to the client when
the headers get flushed.
Example:
response.statusCode = 404;
After response header was sent to the client, this property indicates the
status code which was sent out.
response.statusMessage#
When using implicit headers (not calling response.writeHead() explicitly),
this property controls the status message that will be sent to the client
when the headers get flushed. If this is left as undefined then the standard
message for the status code will be used.
Example:
response.statusMessage = 'Not found';
After response header was sent to the client, this property indicates the
status message which was sent out.
response.write(chunk[, encoding][, callback])#
If this method is called and response.writeHead() has not been called, it
will switch to implicit header mode and flush the implicit headers.
This sends a chunk of the response body. This method may be called
multiple times to provide successive parts of the body.
chunk can be a string or a buffer. If chunk is a string, the second
parameter specifies how to encode it into a byte stream. By default
the encoding is'utf8'. The last parameter callback will be called when this
chunk of data is flushed.
Note: This is the raw HTTP body and has nothing to do with higher-level
multi-part body encodings that may be used.

The first time response.write() is called, it will send the buffered header
information and the first body to the client. The second
time response.write()is called, Node.js assumes you're going to be
streaming data, and sends that separately. That is, the response is
buffered up to the first chunk of body.
Returns true if the entire data was flushed successfully to the kernel
buffer. Returns false if all or part of the data was queued in user
memory. 'drain'will be emitted when the buffer is free again.
response.writeContinue()#
Sends a HTTP/1.1 100 Continue message to the client, indicating that the
request body should be sent. See the 'checkContinue' event on Server.
response.writeHead(statusCode[, statusMessage][, headers])#
Sends a response header to the request. The status code is a 3-digit HTTP
status code, like 404. The last argument, headers, are the response
headers. Optionally one can give a human-readable statusMessage as the
second argument.
Example:
var body = 'hello world';
response.writeHead(200, {
'Content-Length': body.length,
'Content-Type': 'text/plain' });
This method must only be called once on a message and it must be called
before response.end() is called.
If you call response.write() or response.end() before calling this, the
implicit/mutable headers will be calculated and call this function for you.
When headers have been set with response.setHeader(), they will be
merged with any headers passed to response.writeHead(), with the
headers passed to response.writeHead() given precedence.
// returns content-type = text/plain
const server = http.createServer((req,res) => {

res.setHeader('Content-Type', 'text/html');
res.setHeader('X-Foo', 'bar');
res.writeHead(200, {'Content-Type': 'text/plain'});
res.end('ok');
});
Note that Content-Length is given in bytes not characters. The above
example works because the string 'hello world' contains only single byte
characters. If the body contains higher coded characters
then Buffer.byteLength() should be used to determine the number of bytes
in a given encoding. And Node.js does not check whether Content-Length
and the length of the body which has been transmitted are equal or not.
Attempting to set a header field name or value that contains invalid
characters will result in a TypeError being thrown.
Class: http.IncomingMessage#
An IncomingMessage object is created
by http.Server or http.ClientRequest and passed as the first argument to
the 'request' and 'response' event respectively. It may be used to access
response status, headers and data.
It implements the Readable Stream interface, as well as the following
additional events, methods, and properties.
Event: 'close'#
function () { }
Indicates that the underlying connection was closed. Just like 'end', this
event occurs only once per response.
message.headers#
The request/response headers object.
Key-value pairs of header names and values. Header names are lowercased. Example:
// Prints something like:

//
// { 'user-agent': 'curl/7.22.0',
// host: '127.0.0.1:8000',
// accept: '*/*' }
console.log(request.headers);
Duplicates in raw headers are handled in the following ways, depending
on the header name:

Duplicates of age, authorization, content-length, contenttype, etag, expires, from, host, if-modified-since, if-unmodifiedsince,last-modified, location, max-forwards, proxy-authorization, refere
r, retry-after, or user-agent are discarded.
set-cookie is always an array. Duplicates are added to the array.

For all other headers, the values are joined together with ', '.
message.httpVersion#
In case of server request, the HTTP version sent by the client. In the case
of client response, the HTTP version of the connected-to server. Probably
either'1.1' or '1.0'.
Also message.httpVersionMajor is the first integer
and message.httpVersionMinor is the second.
message.method#
Only valid for request obtained from http.Server.
The request method as a string. Read only. Example: 'GET', 'DELETE'.
message.rawHeaders#
The raw request/response headers list exactly as they were received.
Note that the keys and values are in the same list. It is not a list of tuples.
So, the even-numbered offsets are key values, and the odd-numbered
offsets are the associated values.
Header names are not lowercased, and duplicates are not merged.
// Prints something like:

//
// [ 'user-agent',
// 'this is invalid because there can be only one',
// 'User-Agent',
// 'curl/7.22.0',
// 'Host',
// '127.0.0.1:8000',
// 'ACCEPT',
// '*/*' ]
console.log(request.rawHeaders);
message.rawTrailers#
The raw request/response trailer keys and values exactly as they were
received. Only populated at the 'end' event.
message.setTimeout(msecs, callback)#

msecs <Number>

callback <Function>

Calls message.connection.setTimeout(msecs, callback).

Returns message.
message.statusCode#
Only valid for response obtained from http.ClientRequest.
The 3-digit HTTP response status code. E.G. 404.
message.statusMessage#
Only valid for response obtained from http.ClientRequest.
The HTTP response status message (reason phrase). E.G. OK or Internal
Server Error.
message.socket#
The net.Socket object associated with the connection.

With HTTPS support, use request.socket.getPeerCertificate() to obtain the

client's authentication details.
message.trailers#
The request/response trailers object. Only populated at the 'end' event.
message.url#
Only valid for request obtained from http.Server.
Request URL string. This contains only the URL that is present in the
actual HTTP request. If the request is:
GET /status?name=ryan HTTP/1.1\r\n
Accept: text/plain\r\n
\r\n
Then request.url will be:
'/status?name=ryan'
If you would like to parse the URL into its parts, you can
use require('url').parse(request.url). Example:
$ node
> require('url').parse('/status?name=ryan')
{
href: '/status?name=ryan',
search: '?name=ryan',
query: 'name=ryan',
pathname: '/status'
}
If you would like to extract the params from the query string, you can use
the require('querystring').parse function, or pass true as the second
argument to require('url').parse. Example:
$ node
> require('url').parse('/status?name=ryan', true)
{

href: '/status?name=ryan',
search: '?name=ryan',
query: {name: 'ryan'},
pathname: '/status'
}
http.METHODS#

<Array>

A list of the HTTP methods that are supported by the parser.

http.STATUS_CODES#

<Object>

A collection of all the standard HTTP response status codes, and the short
description of each. For example, http.STATUS_CODES[404] === 'Not
Found'.
http.createClient([port][, host])#
Stability: 0 - Deprecated: Use http.request() instead.
Constructs a new HTTP client. port and host refer to the server to be
connected to.
http.createServer([requestListener])#
Returns a new instance of http.Server.
The requestListener is a function which is automatically added to
the 'request' event.
http.get(options[, callback])#
Since most requests are GET requests without bodies, Node.js provides
this convenience method. The only difference between this method
andhttp.request() is that it sets the method to GET and
calls req.end() automatically.
Example:

http.get('http://www.google.com/index.html', (res) => {

console.log(`Got response: ${res.statusCode}`);
// consume response body
res.resume();
}).on('error', (e) => {
console.log(`Got error: ${e.message}`);
});
http.globalAgent#
Global instance of Agent which is used as the default for all http client
requests.
http.request(options[, callback])#
Node.js maintains several connections per server to make HTTP requests.
This function allows one to transparently issue requests.
options can be an object or a string. If options is a string, it is
automatically parsed with url.parse().
Options:

protocol: Protocol to use. Defaults to 'http:'.

host: A domain name or IP address of the server to issue the request

to. Defaults to 'localhost'.

hostname: Alias for host. To support url.parse() hostname is

preferred over host.

family: IP address family to use when resolving host and hostname.

Valid values are 4 or 6. When unspecified, both IP v4 and v6 will be
used.

port: Port of remote server. Defaults to 80.

localAddress: Local interface to bind for network connections.

socketPath: Unix Domain Socket (use one of host:port or

socketPath).

method: A string specifying the HTTP request method. Defaults

to 'GET'.

path: Request path. Defaults to '/'. Should include query string if any.
E.G. '/index.html?page=12'. An exception is thrown when the request
path contains illegal characters. Currently, only spaces are rejected
but that may change in the future.
headers: An object containing request headers.

auth: Basic authentication i.e. 'user:password' to compute an

Authorization header.

agent: Controls Agent behavior. When an Agent is used request will

default to Connection: keep-alive. Possible values:
o

undefined (default): use http.globalAgent for this host and

port.
Agent object: explicitly use the passed in Agent.

o
o

false: opts out of connection pooling with an Agent, defaults

request to Connection: close.

createConnection: A function that produces a socket/stream to use

for the request when the agent option is not used. This can be used to
avoid creating a custom Agent class just to override the
default createConnection function. See agent.createConnection() for
more details.

The optional callback parameter will be added as a one time listener for
the 'response' event.
http.request() returns an instance of the http.ClientRequest class.
The ClientRequest instance is a writable stream. If one needs to upload a
file with a POST request, then write to the ClientRequest object.
Example:
var postData = querystring.stringify({
'msg' : 'Hello World!'
});
var options = {
hostname: 'www.google.com',
port: 80,
path: '/upload',

method: 'POST',
headers: {
'Content-Type': 'application/x-www-form-urlencoded',
'Content-Length': postData.length
}
};
var req = http.request(options, (res) => {
console.log(`STATUS: ${res.statusCode}`);
console.log(`HEADERS: ${JSON.stringify(res.headers)}`);
res.setEncoding('utf8');
res.on('data', (chunk) => {
console.log(`BODY: ${chunk}`);
});
res.on('end', () => {
console.log('No more data in response.')
})
});
req.on('error', (e) => {
console.log(`problem with request: ${e.message}`);
});
// write data to request body
req.write(postData);
req.end();
Note that in the example req.end() was called. With http.request() one
must always call req.end() to signify that you're done with the request even if there is no data being written to the request body.
If any error is encountered during the request (be that with DNS
resolution, TCP level errors, or actual HTTP parse errors) an 'error' event is
emitted on the returned request object. As with all 'error' events, if no
listeners are registered the error will be thrown.
There are a few special headers that should be noted.

Sending a 'Connection: keep-alive' will notify Node.js that the

connection to the server should be persisted until the next request.

Sending a 'Content-length' header will disable the default chunked

encoding.

Sending an 'Expect' header will immediately send the request

headers. Usually, when sending 'Expect: 100-continue', you should
both set a timeout and listen for the 'continue' event. See RFC2616
Section 8.2.3 for more information.

Sending an Authorization header will override using the auth option

to compute basic authentication.

HTTPS#
Stability: 2 - Stable
HTTPS is the HTTP protocol over TLS/SSL. In Node.js this is implemented
as a separate module.
Class: https.Agent#
An Agent object for HTTPS similar to http.Agent. See https.request() for
more information.
Class: https.Server#
This class is a subclass of tls.Server and emits events same
as http.Server. See http.Server for more information.
server.setTimeout(msecs, callback)#
See http.Server#setTimeout().
server.timeout#
See http.Server#timeout.
https.createServer(options[, requestListener])#

Returns a new HTTPS web server object. The options is similar

to tls.createServer(). The requestListener is a function which is
automatically added to the 'request' event.
Example:
// curl -k https://localhost:8000/
const https = require('https');
const fs = require('fs');
const options = {
key: fs.readFileSync('test/fixtures/keys/agent2-key.pem'),
cert: fs.readFileSync('test/fixtures/keys/agent2-cert.pem')
};
https.createServer(options, (req, res) => {
res.writeHead(200);
res.end('hello world\n');
}).listen(8000);
Or
const https = require('https');
const fs = require('fs');
const options = {
pfx: fs.readFileSync('server.pfx')
};
https.createServer(options, (req, res) => {
res.writeHead(200);
res.end('hello world\n');
}).listen(8000);
server.close([callback])#
See http.close() for details.

server.listen(handle[, callback])#
server.listen(path[, callback])#
server.listen(port[, host][, backlog][, callback])#
See http.listen() for details.
https.get(options, callback)#
Like http.get() but for HTTPS.
options can be an object or a string. If options is a string, it is
automatically parsed with url.parse().
Example:
const https = require('https');
https.get('https://encrypted.google.com/', (res) => {
console.log('statusCode: ', res.statusCode);
console.log('headers: ', res.headers);
res.on('data', (d) => {
process.stdout.write(d);
});
}).on('error', (e) => {
console.error(e);
});
https.globalAgent#
Global instance of https.Agent for all HTTPS client requests.
https.request(options, callback)#
Makes a request to a secure web server.
options can be an object or a string. If options is a string, it is
automatically parsed with url.parse().
All options from http.request() are valid.

Example:
const https = require('https');
var options = {
hostname: 'encrypted.google.com',
port: 443,
path: '/',
method: 'GET'
};
var req = https.request(options, (res) => {
console.log('statusCode: ', res.statusCode);
console.log('headers: ', res.headers);
res.on('data', (d) => {
process.stdout.write(d);
});
});
req.end();
req.on('error', (e) => {
console.error(e);
});
The options argument has the following options

host: A domain name or IP address of the server to issue the request

to. Defaults to 'localhost'.

hostname: Alias for host. To support url.parse() hostname is

preferred over host.

family: IP address family to use when resolving host and hostname.

Valid values are 4 or 6. When unspecified, both IP v4 and v6 will be
used.

port: Port of remote server. Defaults to 443.

localAddress: Local interface to bind for network connections.

socketPath: Unix Domain Socket (use one of host:port or

socketPath).

method: A string specifying the HTTP request method. Defaults

to 'GET'.

path: Request path. Defaults to '/'. Should include query string if any.
E.G. '/index.html?page=12'. An exception is thrown when the request
path contains illegal characters. Currently, only spaces are rejected
but that may change in the future.

headers: An object containing request headers.

auth: Basic authentication i.e. 'user:password' to compute an

Authorization header.

agent: Controls Agent behavior. When an Agent is used request will

default to Connection: keep-alive. Possible values:
o

undefined (default): use globalAgent for this host and port.

Agent object: explicitly use the passed in Agent.

false: opts out of connection pooling with an Agent, defaults

request to Connection: close.

The following options from tls.connect() can also be specified. However,

a globalAgent silently ignores these.

pfx: Certificate, Private key and CA certificates to use for SSL.

Default null.
key: Private key to use for SSL. Default null.
passphrase: A string of passphrase for the private key or pfx.
Default null.
cert: Public x509 certificate to use. Default null.

ca: A string, Buffer or array of strings or Buffers of trusted

certificates in PEM format. If this is omitted several well known "root"
CAs will be used, like VeriSign. These are used to authorize
connections.

ciphers: A string describing the ciphers to use or exclude.

Consult https://www.openssl.org/docs/apps/ciphers.html#CIPHER_LIST
_FORMAT for details on the format.

rejectUnauthorized: If true, the server certificate is verified against

the list of supplied CAs. An 'error' event is emitted if verification fails.
Verification happens at the connection level, before the HTTP request
is sent. Default true.

secureProtocol: The SSL method to use, e.g. SSLv3_method to force

SSL version 3. The possible values depend on your installation of
OpenSSL and are defined in the constant SSL_METHODS.

servername: Servername for SNI (Server Name Indication) TLS

extension.

In order to specify these options, use a custom Agent.

Example:
var options = {
hostname: 'encrypted.google.com',
port: 443,
path: '/',
method: 'GET',
key: fs.readFileSync('test/fixtures/keys/agent2-key.pem'),
cert: fs.readFileSync('test/fixtures/keys/agent2-cert.pem')
};
options.agent = new https.Agent(options);
var req = https.request(options, (res) => {
...
}
Alternatively, opt out of connection pooling by not using an Agent.
Example:
var options = {
hostname: 'encrypted.google.com',
port: 443,
path: '/',
method: 'GET',
key: fs.readFileSync('test/fixtures/keys/agent2-key.pem'),
cert: fs.readFileSync('test/fixtures/keys/agent2-cert.pem'),
agent: false

};
var req = https.request(options, (res) => {
...
}

Modules#
Stability: 3 - Locked
Node.js has a simple module loading system. In Node.js, files and modules
are in one-to-one correspondence. As an example, foo.js loads the
modulecircle.js in the same directory.
The contents of foo.js:
const circle = require('./circle.js');
console.log( `The area of a circle of radius 4 is ${circle.area(4)}`);
The contents of circle.js:
const PI = Math.PI;
exports.area = (r) => PI * r * r;
exports.circumference = (r) => 2 * PI * r;
The module circle.js has exported the
functions area() and circumference(). To add functions and objects to the
root of your module, you can add them to the special exports object.
Variables local to the module will be private, because the module is
wrapped in a function by Node.js (see module wrapper). In this example,
the variablePI is private to circle.js.
If you want the root of your module's export to be a function (such as a
constructor) or if you want to export a complete object in one assignment
instead of building it one property at a time, assign it
to module.exports instead of exports.

Below, bar.js makes use of the square module, which exports a

constructor:
const square = require('./square.js');
var mySquare = square(2);
console.log(`The area of my square is ${mySquare.area()}`);
The square module is defined in square.js:
// assigning to exports will not modify module, must use
module.exports
module.exports = (width) => {
return {
area: () => width * width
};
}
The module system is implemented in the require("module") module.
Accessing the main module#
When a file is run directly from Node.js, require.main is set to its module.
That means that you can determine whether a file has been run directly
by testing
require.main === module
For a file foo.js, this will be true if run via node foo.js, but false if run
by require('./foo').
Because module provides a filename property (normally equivalent
to __filename), the entry point of the current application can be obtained
by checking require.main.filename.
Addenda: Package Manager Tips#
The semantics of Node.js's require() function were designed to be general
enough to support a number of reasonable directory structures. Package
manager programs such as dpkg, rpm, and npm will hopefully find it
possible to build native packages from Node.js modules without
modification.

Below we give a suggested directory structure that could work:

Let's say that we wanted to have the folder at /usr/lib/node/<somepackage>/<some-version> hold the contents of a specific version of a
package.
Packages can depend on one another. In order to install package foo, you
may have to install a specific version of package bar. The bar package
may itself have dependencies, and in some cases, these dependencies
may even collide or form cycles.
Since Node.js looks up the realpath of any modules it loads (that is,
resolves symlinks), and then looks for their dependencies in
the node_modulesfolders as described here, this situation is very simple to
resolve with the following architecture:

/usr/lib/node/foo/1.2.3/ - Contents of the foo package, version 1.2.3.

/usr/lib/node/bar/4.3.2/ - Contents of the bar package

that foo depends on.

/usr/lib/node/foo/1.2.3/node_modules/bar - Symbolic link

to /usr/lib/node/bar/4.3.2/.

/usr/lib/node/bar/4.3.2/node_modules/* - Symbolic links to the

packages that bar depends on.

Thus, even if a cycle is encountered, or if there are dependency conflicts,

every module will be able to get a version of its dependency that it can
use.
When the code in the foo package does require('bar'), it will get the
version that is symlinked into /usr/lib/node/foo/1.2.3/node_modules/bar.
Then, when the code in the bar package calls require('quux'), it'll get the
version that is symlinked into/usr/lib/node/bar/4.3.2/node_modules/quux.
Furthermore, to make the module lookup process even more optimal,
rather than putting packages directly in /usr/lib/node, we could put them
in/usr/lib/node_modules/<name>/<version>. Then Node.js will not bother
looking for missing dependencies in /usr/node_modules or /node_modules.

In order to make modules available to the Node.js REPL, it might be useful

to also add the /usr/lib/node_modules folder to
the $NODE_PATH environment variable. Since the module lookups
using node_modules folders are all relative, and based on the real path of
the files making the calls to require(), the packages themselves can be
anywhere.
All Together...#
To get the exact filename that will be loaded when require() is called, use
the require.resolve() function.
Putting together all of the above, here is the high-level algorithm in
pseudocode of what require.resolve does:
require(X) from module at path Y
1. If X is a core module,
a. return the core module
b. STOP
2. If X begins with './' or '/' or '../'
a. LOAD_AS_FILE(Y + X)
b. LOAD_AS_DIRECTORY(Y + X)
3. LOAD_NODE_MODULES(X, dirname(Y))
4. THROW "not found"
LOAD_AS_FILE(X)
1. If X is a file, load X as JavaScript text. STOP
2. If X.js is a file, load X.js as JavaScript text. STOP
3. If X.json is a file, parse X.json to a JavaScript Object. STOP
4. If X.node is a file, load X.node as binary addon. STOP
LOAD_AS_DIRECTORY(X)
1. If X/package.json is a file,
a. Parse X/package.json, and look for "main" field.
b. let M = X + (json main field)
c. LOAD_AS_FILE(M)
2. If X/index.js is a file, load X/index.js as JavaScript text. STOP
3. If X/index.json is a file, parse X/index.json to a JavaScript object.
STOP

4. If X/index.node is a file, load X/index.node as binary addon. STOP

LOAD_NODE_MODULES(X, START)
1. let DIRS=NODE_MODULES_PATHS(START)
2. for each DIR in DIRS:
a. LOAD_AS_FILE(DIR/X)
b. LOAD_AS_DIRECTORY(DIR/X)
NODE_MODULES_PATHS(START)
1. let PARTS = path split(START)
2. let I = count of PARTS - 1
3. let DIRS = []
4. while I >= 0,
a. if PARTS[I] = "node_modules" CONTINUE
c. DIR = path join(PARTS[0 .. I] + "node_modules")
b. DIRS = DIRS + DIR
c. let I = I - 1
5. return DIRS
Caching#
Modules are cached after the first time they are loaded. This means
(among other things) that every call to require('foo') will get exactly the
same object returned, if it would resolve to the same file.
Multiple calls to require('foo') may not cause the module code to be
executed multiple times. This is an important feature. With it, "partially
done" objects can be returned, thus allowing transitive dependencies to
be loaded even when they would cause cycles.
If you want to have a module execute code multiple times, then export a
function, and call that function.
Module Caching Caveats#
Modules are cached based on their resolved filename. Since modules may
resolve to a different filename based on the location of the calling module
(loading from node_modules folders), it is not
a guarantee that require('foo') will always return the exact same object, if
it would resolve to different files.

Additionally, on case-insensitive file systems or operating systems,

different resolved filenames can point to the same file, but the cache will
still treat them as different modules and will reload the file multiple times.
For example, require('./foo') and require('./FOO') return two different
objects, irrespective of whether or not ./foo and ./FOO are the same file.
Core Modules#
Node.js has several modules compiled into the binary. These modules are
described in greater detail elsewhere in this documentation.
The core modules are defined within Node.js's source and are located in
the lib/ folder.
Core modules are always preferentially loaded if their identifier is passed
to require(). For instance, require('http') will always return the built in
HTTP module, even if there is a file by that name.
Cycles#
When there are circular require() calls, a module might not have finished
executing when it is returned.
Consider this situation:
a.js:
console.log('a starting');
exports.done = false;
const b = require('./b.js');
console.log('in a, b.done = %j', b.done);
exports.done = true;
console.log('a done');
b.js:
console.log('b starting');
exports.done = false;
const a = require('./a.js');
console.log('in b, a.done = %j', a.done);
exports.done = true;

console.log('b done');
main.js:
console.log('main starting');
const a = require('./a.js');
const b = require('./b.js');
console.log('in main, a.done=%j, b.done=%j', a.done, b.done);
When main.js loads a.js, then a.js in turn loads b.js. At that point, b.js tries
to load a.js. In order to prevent an infinite loop, an unfinished copyof
the a.js exports object is returned to the b.js module. b.js then finishes
loading, and its exports object is provided to the a.js module.
By the time main.js has loaded both modules, they're both finished. The
output of this program would thus be:
$ node main.js
main starting
a starting
b starting
in b, a.done = false
b done
in a, b.done = true
a done
in main, a.done=true, b.done=true
If you have cyclic module dependencies in your program, make sure to
plan accordingly.
File Modules#
If the exact filename is not found, then Node.js will attempt to load the
required filename with the added extensions: .js, .json, and finally .node.
.js files are interpreted as JavaScript text files, and .json files are parsed as
JSON text files. .node files are interpreted as compiled addon modules
loaded with dlopen.

A required module prefixed with '/' is an absolute path to the file. For
example, require('/home/marco/foo.js') will load the file
at/home/marco/foo.js.
A required module prefixed with './' is relative to the file calling require().
That is, circle.js must be in the same directory
as foo.js forrequire('./circle') to find it.
Without a leading '/', './', or '../' to indicate a file, the module must either
be a core module or is loaded from a node_modules folder.
If the given path does not exist, require() will throw an Error with
its code property set to 'MODULE_NOT_FOUND'.
Folders as Modules#
It is convenient to organize programs and libraries into self-contained
directories, and then provide a single entry point to that library. There are
three ways in which a folder may be passed to require() as an argument.
The first is to create a package.json file in the root of the folder, which
specifies a main module. An example package.json file might look like
this:
{ "name" : "some-library",
"main" : "./lib/some-library.js" }
If this was in a folder at ./some-library, then require('./some-library') would
attempt to load ./some-library/lib/some-library.js.
This is the extent of Node.js's awareness of package.json files.
Note: If the file specified by the "main" entry of package.json is missing
and can not be resolved, Node.js will report the entire module as missing
with the default error:
Error: Cannot find module 'some-library'
If there is no package.json file present in the directory, then Node.js will
attempt to load an index.js or index.node file out of that directory. For

example, if there was no package.json file in the above example,

then require('./some-library') would attempt to load:

./some-library/index.js

./some-library/index.node

Loading from node_modules Folders#

If the module identifier passed to require() is not a native module, and
does not begin with '/', '../', or './', then Node.js starts at the parent
directory of the current module, and adds /node_modules, and attempts to
load the module from that location. Node will not append node_modules to
a path already ending in node_modules.
If it is not found there, then it moves to the parent directory, and so on,
until the root of the file system is reached.
For example, if the file at '/home/ry/projects/foo.js' called require('bar.js'),
then Node.js would look in the following locations, in this order:

/home/ry/projects/node_modules/bar.js

/home/ry/node_modules/bar.js

/home/node_modules/bar.js

/node_modules/bar.js

This allows programs to localize their dependencies, so that they do not

clash.
You can require specific files or sub modules distributed with a module by
including a path suffix after the module name. For
instance require('example-module/path/to/file') would
resolve path/to/file relative to where example-module is located. The
suffixed path follows the same module resolution semantics.
Loading from the global folders#
If the NODE_PATH environment variable is set to a colon-delimited list of
absolute paths, then Node.js will search those paths for modules if they

are not found elsewhere. (Note: On Windows, NODE_PATH is delimited by

semicolons instead of colons.)
NODE_PATH was originally created to support loading modules from
varying paths before the current module resolution algorithm was frozen.
NODE_PATH is still supported, but is less necessary now that the Node.js
ecosystem has settled on a convention for locating dependent modules.
Sometimes deployments that rely on NODE_PATH show surprising
behavior when people are unaware that NODE_PATH must be set.
Sometimes a module's dependencies change, causing a different version
(or even a different module) to be loaded as the NODE_PATH is searched.
Additionally, Node.js will search in the following locations:

1: $HOME/.node_modules

2: $HOME/.node_libraries

3: $PREFIX/lib/node

Where $HOME is the user's home directory, and $PREFIX is Node.js's

configured node_prefix.
These are mostly for historic reasons. You are highly encouraged to
place your dependencies locally in node_modules folders. They will
be loaded faster, and more reliably.
The module wrapper#
Before a module's code is executed, Node.js will wrap it with a function
wrapper that looks like the following:
(function (exports, require, module, __filename, __dirname) {
// Your module code actually lives in here
});
By doing this, Node.js achieves a few things:

It keeps top-level variables (defined with var, const or let) scoped to

the module rather than the global object.

It helps to provide some global-looking variables that are actually

specific to the module, such as:
o

The module and exports objects that the implementor can use
to export values from the module.

The convenience variables __filename and __dirname,

containing the module's absolute filename and directory path.

The module Object#

<Object>

In each module, the module free variable is a reference to the object

representing the current module. For convenience, module.exports is also
accessible via the exports module-global. module isn't actually a global
but rather local to each module.
module.children#

<Array>

The module objects required by this one.

module.exports#

<Object>

The module.exports object is created by the Module system. Sometimes

this is not acceptable; many want their module to be an instance of some
class. To do this, assign the desired export object to module.exports. Note
that assigning the desired object to exports will simply rebind the
local exportsvariable, which is probably not what you want to do.
For example suppose we were making a module called a.js
const EventEmitter = require('events');
module.exports = new EventEmitter();
// Do some work, and after some time emit
// the 'ready' event from the module itself.
setTimeout(() => {

module.exports.emit('ready');
}, 1000);
Then in another file we could do
const a = require('./a');
a.on('ready', () => {
console.log('module a is ready');
});
Note that assignment to module.exports must be done immediately. It
cannot be done in any callbacks. This does not work:
x.js:
setTimeout(() => {
module.exports = { a: 'hello' };
}, 0);
y.js:
const x = require('./x');
console.log(x.a);

exports alias#

The exports variable that is available within a module starts as a reference

to module.exports. As with any variable, if you assign a new value to it, it
is no longer bound to the previous value.
To illustrate the behavior, imagine this hypothetical implementation
of require():
function require(...) {
// ...
((module, exports) => {
// Your module code here
exports = some_func;
// re-assigns exports, exports is no longer
// a shortcut, and nothing is exported.
module.exports = some_func; // makes your module export 0
})(module, module.exports);
return module;

}
As a guideline, if the relationship
between exports and module.exports seems like magic to you,
ignore exports and only use module.exports.
module.filename#

<String>

The fully resolved filename to the module.

module.id#

<String>

The identifier for the module. Typically this is the fully resolved filename.
module.loaded#

<Boolean>

Whether or not the module is done loading, or is in the process of loading.

module.parent#

<Object> Module object

The module that first required this one.

module.require(id)#

id <String>

Return: <Object> module.exports from the resolved module

The module.require method provides a way to load a module as

if require() was called from the original module.
Note that in order to do this, you must get a reference to
the module object. Since require() returns the module.exports, and
the module is typicallyonly available within a specific module's code, it
must be explicitly exported in order to be used.