Unhandled rejection error network error

I have spent the weekend attempting to resolve this issue, and I believe this to be a bug in axios-mock-adapter. Having said that, if that is not the case, I hope that someone could point out the flaw in the code below. The documentation on the networkError() function is sparse to say the least, and no amount of stackoverflow.com goodness seems to shed any additional light on this one.

My project uses axios-mock-adapter at 1.14.1, and I am attempting to simulate a network error (also a timeout, but one thing at a time). I have attempted to cover all the bases in an attempt to trap the Unhandled Promise Rejection that is reported by Node, so the code below is perhaps a bit more verbose than it needs to be. (Happy to receive any pointers…)

  return axios(data)
    .then((response) => {
      console.log('response',response)
      if (response.data.order === null) { // No order placed yet
        console.log('response.data.order === null', response.data.order === null)
        return {
          status: response.status,
          id: memberId,
          ...
        };
      }
      const { results_ready } = response.data.order; // eslint-disable-line camelcase
      console.log('results_ready', results_ready);
      return {
        status: response.status,
        id: memberId,
        dataReady: results_ready !== null, // eslint-disable-line camelcase
      };
    }, (err) => {
      console.log('err', err);
      if (err.response && err.response.data) {
        console.log('err.response && err.response.data');
        return {
          status: err.response.status,
          message: err.response.data.message,
        };
      }
      // Handle network errors and timeouts
      if (err.code === 'ECONNABORTED' || !err.response.status) {
        console.log('err.code === ECONNABORTED || !err.response.status');
        const result = {
          status: 500,
          message: 'Failed due to network errors',
        };
        console.log('returning', result);
        return result;
      }
      console.log('throwing', err);
      // Throw the remainder
      throw err;
    })
    .catch((err) => {
      console.log('catching', err);
      if (err.response && err.response.data) {
        console.log('catch: err.response && err.response.data');
        // This is a programmer error, or a change in configuration on vendor API side.
        if (err.response.status === 401) {
          console.log('catch: err.response.status === 401');
          throw err;
        }
        // Some other error occurred. Return the stock error information.
        return {
          status: err.response.status,
          message: err.response.data.message,
        };
      }
      console.log('throwing', err);
      debug(err);
      throw err;
    });

The code to test is a follows:

  test('it handles network errors correctly', (done) => {
    const expectedResponse = {
      status: 500,
      message: 'Failed due to network errors',
    };

    mock.onGet(ORDER_API_CALL).networkError();

    getOrderStatus(VALID_MEMBER_ID)
      .then((resp) => {
        console.log('call return', resp);
        expect(resp).toEqual(expectedResponse);
        done();
      }, err => console.log('mystery', err))
      .catch((err) => {
        console.log('call error caught', err); // eslint-disable-line no-console
        done();
      });
  });

The output received when the test runs is:

(node:14986) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1190): Error: Network Error
    ...
    console.log api/.../index.js:129
      err { Error: Request failed with status code undefined
          at createErrorResponse (/home/.../node_modules/axios-mock-adapter/src/utils.js:117:15)
          at Object.settle (/home/.../node_modules/axios-mock-adapter/src/utils.js:97:16)
          at handleRequest (/home/.../node_modules/axios-mock-adapter/src/handle_request.js:51:15)
          at /home/.../node_modules/axios-mock-adapter/src/index.js:18:9
          at new Promise (<anonymous>)
          at MockAdapter.<anonymous> (/home/.../node_modules/axios-mock-adapter/src/index.js:17:14)
          at dispatchRequest (/home/.../node_modules/axios/lib/core/dispatchRequest.js:59:10)
          at <anonymous>
          at process._tickCallback (internal/process/next_tick.js:188:7)
        config: 
         { adapter: null,
           transformRequest: { '0': [Function: transformRequest] },
           transformResponse: { '0': [Function: transformResponse] },
           timeout: 0,
           xsrfCookieName: 'XSRF-TOKEN',
           xsrfHeaderName: 'X-XSRF-TOKEN',
           maxContentLength: -1,
           validateStatus: [Function: validateStatus],
           headers: 
            { Accept: 'application/json, text/plain, */*',
              Authorization: 'API-KEY undefined' },
           method: 'get',
           url: 'https://.../order',
           data: undefined },
        response: 
         { status: undefined,
           data: undefined,
           headers: undefined,
           config: 
            { adapter: null,
              transformRequest: [Object],
              transformResponse: [Object],
              timeout: 0,
              xsrfCookieName: 'XSRF-TOKEN',
              xsrfHeaderName: 'X-XSRF-TOKEN',
              maxContentLength: -1,
              validateStatus: [Function: validateStatus],
              headers: [Object],
              method: 'get',
              url: 'https://.../order',
              data: undefined } } }
    console.log api/.../index.js:139
      err.code === ECONNABORTED || !err.response.status
    console.log api/.../index.js:144
      returning { status: 500, message: 'Failed due to network errors' }
    console.log api/.../....test.js:323
      call return { status: 500, message: 'Failed due to network errors' }

Thanks for looking into this issue. Has me stumped!

An Animated Guide to Node.js Event Lop

Node.js doesn’t stop from running other operations because of Libuv, a C++ library responsible for the event loop and asynchronously handling tasks such as network requests, DNS resolution, file system operations, data encryption, etc.

What happens under the hood when Node.js works on tasks such as database queries? We will explore it by following this piece of code step by step.

Node.js 6.6.0 added a sporadically useful bug/feature: logging unhandled promise rejections to the console by default. In other words, the below script will print an error to the console:

Promise.reject(new Error('woops'));

/* Output:
$ node test.js
(node:7741) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: woops
(node:7741) DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code. */

Bluebird has supported similar behavior for quite a while. I’ve vocally expressed my distaste for this behavior in the past, it’s actually one of the many reasons why I don’t use bluebird. But now that this behavior is in core node, it appears we’re all stuck with it, so we better learn to take advantage of it.

What is an Unhandled Rejection?

«Rejection» is the canonical term for a promise reporting an error. As defined in ES6, a promise is a state machine representation of an asynchronous operation and can be in one of 3 states: «pending», «fulfilled», or «rejected». A pending promise represents an asynchronous operation that’s in progress and a fulfilled promise represents an asynchronous operation that’s completed successfully. A rejected promise represents an asynchronous operation that failed for some reason. For example, trying to connect to a nonexistent MongoDB instance using the MongoDB driver will give you a promise rejection:

const { MongoClient } = require('mongodb');

MongoClient.connect('mongodb://notadomain');

/* Output:
$ node test.js
(node:9563) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): MongoError: failed to connect to server [notadomain:27017] on first connect [MongoError: getaddrinfo ENOTFOUND notadomain notadomain:27017]
(node:9563) DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code. */

Recall that the ES6 style promise constructor takes an «executor» function that takes 2 functions as arguments, resolve and reject. One way to cause a promise rejection is to call reject():

new Promise((resolve, reject) => {
  setTimeout(() => reject('woops'), 500);
});

/* Output:
$ node test.js
(node:8128) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): woops
(node:8128) DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code. */

Another way is to throw an exception in the executor function:

new Promise(() => { throw new Error('exception!'); });

/* Output
$ node test.js
(node:8383) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: exception!
(node:8383) DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code. */

Some argue that throwing an exception in the executor function is bad practice. I strongly disagree. Consolidated error handling is a strong design pattern, and going back to the days where we had to wrap async function calls in try/catch as well as handle the callback error param is a step in the wrong direction.

Chaining is how you handle promise rejections. ES6 promises have a handy .catch() helper function for handling rejections.

new Promise((_, reject) => reject(new Error('woops'))).
  // Prints "caught woops"
  catch(error => { console.log('caught', error.message); });

// Equivalent. `.catch(fn)` is essentially identical to `.then(null, fn)`
new Promise((_, reject) => reject(new Error('woops'))).
  // Prints "caught woops"
  then(null, error => { console.log('caught', error.message); });

Seems easy, right? How about the below code, what will it print?

new Promise((_, reject) => reject(new Error('woops'))).
  catch(error => { console.log('caught', err.message); });

It’ll print out an unhandled rejection warning. Notice that err is not defined!

$ node test.js
(node:9825) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 2): ReferenceError: err is not defined
(node:9825) DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

This is why unhandled rejections can be so insidious. You might think you caught an error, but your error handler might have caused another error. You get a similar problem if you return a promise in your .catch() function. For example, let’s say you use an misconfigured sentry client for logging errors and return a promise representing tracking the error to sentry.

const sentry = require('raven');

new Promise((_, reject) => reject(new Error('woops'))).
  catch(error => new Promise((resolve, reject) => {
    sentry.captureMessage(error.message, function(error) {
      if (error) {
        return reject(error);
      }
      resolve();
    });
  }));

/* Output
$ node test.js
(node:10019) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 3): TypeError: Cannot read property 'user' of undefined
(node:10019) DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
*/

There are a lot of nasty gotchas with unhandled rejections. That’s why Node.js gives you a mechanism for globally handling unhandled rejections.

The unhandledRejection Event

The node process global has an unhandledRejection event for unhandled promise rejection. Bluebird also emits this event, so if you do global.Promise = require('bluebird') the below code will still work. Your event handler will receive the promise rejection error as its first parameter:

process.on('unhandledRejection', error => {
  // Will print "unhandledRejection err is not defined"
  console.log('unhandledRejection', error.message);
});

new Promise((_, reject) => reject(new Error('woops'))).
  catch(error => {
    // Will not execute
    console.log('caught', err.message);
  });

Note that, while the error parameter to the ‘unhandledRejection’ event should be a JavaScript error, it doesn’t necessarily have to be. Calling reject() with a non-error is considered bad practice, but if you do, ‘unhandledRejection’ will get the argument you passed to reject().

process.on('unhandledRejection', error => {
  // Prints "unhandledRejection woops!"
  console.log('unhandledRejection', error.test);
});

new Promise((_, reject) => reject({ test: 'woops!' }));

Note that if you attach a listener to ‘unhandledRejection’, the default warning to the console (the UnhandledPromiseRejectionWarning from previous examples) will not print to the console. That message only gets printed if you don’t have a handler for ‘unhandledRejection’.

If you want to suppress the unhandled promise rejection warning, all you need to do is call .catch() on the promise with an empty function.

process.on('unhandledRejection', error => {
  // Won't execute
  console.log('unhandledRejection', error.test);
});

new Promise((_, reject) => reject({ test: 'woops!' })).catch(() => {});

This is how you suppress unhandled rejection handling when you’re absolutely sure you don’t want to handle the error. Why would you want to suppress unhandled rejection handling? Let’s say you used sinon to stub out a function that returns a promise in a mocha before() test hook. The below test succeeds:

const sinon = require('sinon');

const obj = {
  fn: () => {}
};

before(function() {
  sinon.stub(obj, 'fn').returns(Promise.resolve());
});

it('works', function() {
  return obj.fn();
});

However, what if you want to stub out obj.fn() to return a promise that rejects? The below script will log an unhandled rejection warning:

const assert = require('assert');
const sinon = require('sinon');

const obj = {
  fn: () => {}
};

before(function() {
  sinon.stub(obj, 'fn').returns(Promise.reject(new Error('test')));
});

it('works', function() {
  return obj.fn().catch(error => {
    assert.equal(error.message, 'test');
  });
});

This is where ‘unhandledRejection’ starts breaking down the abstraction barriers of promises. Now, .catch() is no longer a pure function and has global side effects. For example, one way to avoid the unhandled rejection warning above is to call .catch() on the promise but not use the promise that .catch() returns:

before(function() {
  const p = Promise.reject(new Error('test'));
  p.catch(() => {});
  // No more warning! `.catch()` mutates `p`'s internal state.
  sinon.stub(obj, 'fn').returns(p);
});

Implications for Async/Await

Async/await has a major advantage over building promise chains manually: await handles .catch() for you. For example:

async function test() {
  // No unhandled rejection!
  await Promise.reject(new Error('test'));
}

test().catch(() => {});

However, notice the .catch() call chained onto test(). Remember that an async function returns a promise! No .catch() there will give you an unhandled rejection.

async function test() {
  // No unhandled rejection!
  await Promise.reject(new Error('test'));
}

test();

/* Output:
$ node test.js
(node:13912) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 2): Error: test
(node:13912) DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code. */

Async/await lets you construct promises that represent complex operations involving loops, conditionals, etc., but in the end you still get a promise back. Remember to handle your errors!

In case you were wondering, you cannot make async functions return a non-native promise. So there’s no way to make a promise library that bypasses node’s unhandled rejection handler and integrates with async/await.

global.Promise = require('bluebird');

async function test() {
  // No unhandled rejection!
  await Promise.reject(new Error('test'));
}

// Prints "false"
console.log(test().catch(() => {}) instanceof require('bluebird'));

Confused by promise chains? Async/await is the best way to compose promises in Node.js.
Await handles promise rejections for you, so unhandled promise rejections go away. My new ebook, Mastering Async/Await, is designed to give you an integrated understanding of
async/await fundamentals and how async/await fits in the JavaScript ecosystem in a few hours. Get your copy!

Looking to become fluent in async/await? My new ebook, Mastering Async/Await, is designed to give you an integrated understanding of
async/await fundamentals and how async/await fits in the JavaScript ecosystem in a few hours. Get your copy!

Unhandled Promise Rejections in Node.js

Node.js 6.6.0 added a sporadically useful bug/feature: logging unhandled promise rejections to the console by default. In other words, the below script will print an error to the console:

Bluebird has supported similar behavior for quite a while. I’ve vocally expressed my distaste for this behavior in the past, it’s actually one of the many reasons why I don’t use bluebird. But now that this behavior is in core node, it appears we’re all stuck with it, so we better learn to take advantage of it.

What is an Unhandled Rejection?

«Rejection» is the canonical term for a promise reporting an error. As defined in ES6, a promise is a state machine representation of an asynchronous operation and can be in one of 3 states: «pending», «fulfilled», or «rejected». A pending promise represents an asynchronous operation that’s in progress and a fulfilled promise represents an asynchronous operation that’s completed successfully. A rejected promise represents an asynchronous operation that failed for some reason. For example, trying to connect to a nonexistent MongoDB instance using the MongoDB driver will give you a promise rejection:

Recall that the ES6 style promise constructor takes an «executor» function that takes 2 functions as arguments, resolve and reject . One way to cause a promise rejection is to call reject() :

Another way is to throw an exception in the executor function:

Some argue that throwing an exception in the executor function is bad practice. I strongly disagree. Consolidated error handling is a strong design pattern, and going back to the days where we had to wrap async function calls in try/catch as well as handle the callback error param is a step in the wrong direction.

Chaining is how you handle promise rejections. ES6 promises have a handy .catch() helper function for handling rejections.

Seems easy, right? How about the below code, what will it print?

It’ll print out an unhandled rejection warning. Notice that err is not defined!

This is why unhandled rejections can be so insidious. You might think you caught an error, but your error handler might have caused another error. You get a similar problem if you return a promise in your .catch() function. For example, let’s say you use an misconfigured sentry client for logging errors and return a promise representing tracking the error to sentry.

There are a lot of nasty gotchas with unhandled rejections. That’s why Node.js gives you a mechanism for globally handling unhandled rejections.

The unhandledRejection Event

The node process global has an unhandledRejection event for unhandled promise rejection. Bluebird also emits this event, so if you do global.Promise = require(‘bluebird’) the below code will still work. Your event handler will receive the promise rejection error as its first parameter:

Note that, while the error parameter to the ‘unhandledRejection’ event should be a JavaScript error, it doesn’t necessarily have to be. Calling reject() with a non-error is considered bad practice, but if you do, ‘unhandledRejection’ will get the argument you passed to reject() .

Note that if you attach a listener to ‘unhandledRejection’, the default warning to the console (the UnhandledPromiseRejectionWarning from previous examples) will not print to the console. That message only gets printed if you don’t have a handler for ‘unhandledRejection’.

If you want to suppress the unhandled promise rejection warning, all you need to do is call .catch() on the promise with an empty function.

This is how you suppress unhandled rejection handling when you’re absolutely sure you don’t want to handle the error. Why would you want to suppress unhandled rejection handling? Let’s say you used sinon to stub out a function that returns a promise in a mocha before() test hook. The below test succeeds:

However, what if you want to stub out obj.fn() to return a promise that rejects? The below script will log an unhandled rejection warning:

This is where ‘unhandledRejection’ starts breaking down the abstraction barriers of promises. Now, .catch() is no longer a pure function and has global side effects. For example, one way to avoid the unhandled rejection warning above is to call .catch() on the promise but not use the promise that .catch() returns:

Implications for Async/Await

Async/await has a major advantage over building promise chains manually: await handles .catch() for you. For example:

However, notice the .catch() call chained onto test() . Remember that an async function returns a promise! No .catch() there will give you an unhandled rejection.

Async/await lets you construct promises that represent complex operations involving loops, conditionals, etc., but in the end you still get a promise back. Remember to handle your errors!

In case you were wondering, you cannot make async functions return a non-native promise. So there’s no way to make a promise library that bypasses node’s unhandled rejection handler and integrates with async/await.

Confused by promise chains? Async/await is the best way to compose promises in Node.js. Await handles promise rejections for you, so unhandled promise rejections go away. My new ebook, Mastering Async/Await, is designed to give you an integrated understanding of async/await fundamentals and how async/await fits in the JavaScript ecosystem in a few hours. Get your copy!

Looking to become fluent in async/await? My new ebook, Mastering Async/Await, is designed to give you an integrated understanding of async/await fundamentals and how async/await fits in the JavaScript ecosystem in a few hours. Get your copy!

Источник

Node.js v19.4.0 documentation

Process #

Source Code: lib/process.js

The process object provides information about, and control over, the current Node.js process.

Process events #

The process object is an instance of EventEmitter .

Event: ‘beforeExit’ #

The ‘beforeExit’ event is emitted when Node.js empties its event loop and has no additional work to schedule. Normally, the Node.js process will exit when there is no work scheduled, but a listener registered on the ‘beforeExit’ event can make asynchronous calls, and thereby cause the Node.js process to continue.

The listener callback function is invoked with the value of process.exitCode passed as the only argument.

The ‘beforeExit’ event is not emitted for conditions causing explicit termination, such as calling process.exit() or uncaught exceptions.

The ‘beforeExit’ should not be used as an alternative to the ‘exit’ event unless the intention is to schedule additional work.

Event: ‘disconnect’ #

If the Node.js process is spawned with an IPC channel (see the Child Process and Cluster documentation), the ‘disconnect’ event will be emitted when the IPC channel is closed.

Event: ‘exit’ #

The ‘exit’ event is emitted when the Node.js process is about to exit as a result of either:

• The process.exit() method being called explicitly;
• The Node.js event loop no longer having any additional work to perform.

There is no way to prevent the exiting of the event loop at this point, and once all ‘exit’ listeners have finished running the Node.js process will terminate.

The listener callback function is invoked with the exit code specified either by the process.exitCode property, or the exitCode argument passed to the process.exit() method.

Listener functions must only perform synchronous operations. The Node.js process will exit immediately after calling the ‘exit’ event listeners causing any additional work still queued in the event loop to be abandoned. In the following example, for instance, the timeout will never occur:

Event: ‘message’ #

• message | | | | a parsed JSON object or a serializable primitive value.
• sendHandle | a net.Server or net.Socket object, or undefined.

If the Node.js process is spawned with an IPC channel (see the Child Process and Cluster documentation), the ‘message’ event is emitted whenever a message sent by a parent process using childprocess.send() is received by the child process.

The message goes through serialization and parsing. The resulting message might not be the same as what is originally sent.

If the serialization option was set to advanced used when spawning the process, the message argument can contain data that JSON is not able to represent. See Advanced serialization for child_process for more details.

Event: ‘multipleResolves’ #

• type The resolution type. One of ‘resolve’ or ‘reject’ .
• promise

The ‘multipleResolves’ event is emitted whenever a Promise has been either:

• Resolved more than once.
• Rejected more than once.
• Rejected after resolve.
• Resolved after reject.

This is useful for tracking potential errors in an application while using the Promise constructor, as multiple resolutions are silently swallowed. However, the occurrence of this event does not necessarily indicate an error. For example, Promise.race() can trigger a ‘multipleResolves’ event.

Because of the unreliability of the event in cases like the Promise.race() example above it has been deprecated.

Event: ‘rejectionHandled’ #

The late handled promise.

The ‘rejectionHandled’ event is emitted whenever a Promise has been rejected and an error handler was attached to it (using promise.catch() , for example) later than one turn of the Node.js event loop.

The Promise object would have previously been emitted in an ‘unhandledRejection’ event, but during the course of processing gained a rejection handler.

There is no notion of a top level for a Promise chain at which rejections can always be handled. Being inherently asynchronous in nature, a Promise rejection can be handled at a future point in time, possibly much later than the event loop turn it takes for the ‘unhandledRejection’ event to be emitted.

Another way of stating this is that, unlike in synchronous code where there is an ever-growing list of unhandled exceptions, with Promises there can be a growing-and-shrinking list of unhandled rejections.

In synchronous code, the ‘uncaughtException’ event is emitted when the list of unhandled exceptions grows.

In asynchronous code, the ‘unhandledRejection’ event is emitted when the list of unhandled rejections grows, and the ‘rejectionHandled’ event is emitted when the list of unhandled rejections shrinks.

In this example, the unhandledRejections Map will grow and shrink over time, reflecting rejections that start unhandled and then become handled. It is possible to record such errors in an error log, either periodically (which is likely best for long-running application) or upon process exit (which is likely most convenient for scripts).

Event: ‘uncaughtException’ #

History

Added the origin argument.

• err The uncaught exception.
• origin Indicates if the exception originates from an unhandled rejection or from a synchronous error. Can either be ‘uncaughtException’ or ‘unhandledRejection’ . The latter is used when an exception happens in a Promise based async context (or if a Promise is rejected) and —unhandled-rejections flag set to strict or throw (which is the default) and the rejection is not handled, or when a rejection happens during the command line entry point’s ES module static loading phase.

The ‘uncaughtException’ event is emitted when an uncaught JavaScript exception bubbles all the way back to the event loop. By default, Node.js handles such exceptions by printing the stack trace to stderr and exiting with code 1, overriding any previously set process.exitCode . Adding a handler for the ‘uncaughtException’ event overrides this default behavior. Alternatively, change the process.exitCode in the ‘uncaughtException’ handler which will result in the process exiting with the provided exit code. Otherwise, in the presence of such handler the process will exit with 0.

It is possible to monitor ‘uncaughtException’ events without overriding the default behavior to exit the process by installing a ‘uncaughtExceptionMonitor’ listener.

Warning: Using ‘uncaughtException’ correctly #

‘uncaughtException’ is a crude mechanism for exception handling intended to be used only as a last resort. The event should not be used as an equivalent to On Error Resume Next . Unhandled exceptions inherently mean that an application is in an undefined state. Attempting to resume application code without properly recovering from the exception can cause additional unforeseen and unpredictable issues.

Exceptions thrown from within the event handler will not be caught. Instead the process will exit with a non-zero exit code and the stack trace will be printed. This is to avoid infinite recursion.

Attempting to resume normally after an uncaught exception can be similar to pulling out the power cord when upgrading a computer. Nine out of ten times, nothing happens. But the tenth time, the system becomes corrupted.

The correct use of ‘uncaughtException’ is to perform synchronous cleanup of allocated resources (e.g. file descriptors, handles, etc) before shutting down the process. It is not safe to resume normal operation after ‘uncaughtException’ .

To restart a crashed application in a more reliable way, whether ‘uncaughtException’ is emitted or not, an external monitor should be employed in a separate process to detect application failures and recover or restart as needed.

Event: ‘uncaughtExceptionMonitor’ #

• err The uncaught exception.
• origin Indicates if the exception originates from an unhandled rejection or from synchronous errors. Can either be ‘uncaughtException’ or ‘unhandledRejection’ . The latter is used when an exception happens in a Promise based async context (or if a Promise is rejected) and —unhandled-rejections flag set to strict or throw (which is the default) and the rejection is not handled, or when a rejection happens during the command line entry point’s ES module static loading phase.

The ‘uncaughtExceptionMonitor’ event is emitted before an ‘uncaughtException’ event is emitted or a hook installed via process.setUncaughtExceptionCaptureCallback() is called.

Installing an ‘uncaughtExceptionMonitor’ listener does not change the behavior once an ‘uncaughtException’ event is emitted. The process will still crash if no ‘uncaughtException’ listener is installed.

Event: ‘unhandledRejection’ #

History

Not handling Promise rejections is deprecated.

Unhandled Promise rejections will now emit a process warning.

The rejected promise.

The ‘unhandledRejection’ event is emitted whenever a Promise is rejected and no error handler is attached to the promise within a turn of the event loop. When programming with Promises, exceptions are encapsulated as «rejected promises». Rejections can be caught and handled using promise.catch() and are propagated through a Promise chain. The ‘unhandledRejection’ event is useful for detecting and keeping track of promises that were rejected whose rejections have not yet been handled.

The following will also trigger the ‘unhandledRejection’ event to be emitted:

In this example case, it is possible to track the rejection as a developer error as would typically be the case for other ‘unhandledRejection’ events. To address such failures, a non-operational .catch(() => < >) handler may be attached to resource.loaded , which would prevent the ‘unhandledRejection’ event from being emitted.

Event: ‘warning’ #

• warning Key properties of the warning are:
  • name The name of the warning. Default: ‘Warning’ .
  • message A system-provided description of the warning.
  • stack A stack trace to the location in the code where the warning was issued.

The ‘warning’ event is emitted whenever Node.js emits a process warning.

A process warning is similar to an error in that it describes exceptional conditions that are being brought to the user’s attention. However, warnings are not part of the normal Node.js and JavaScript error handling flow. Node.js can emit warnings whenever it detects bad coding practices that could lead to sub-optimal application performance, bugs, or security vulnerabilities.

By default, Node.js will print process warnings to stderr . The —no-warnings command-line option can be used to suppress the default console output but the ‘warning’ event will still be emitted by the process object.

The following example illustrates the warning that is printed to stderr when too many listeners have been added to an event:

In contrast, the following example turns off the default warning output and adds a custom handler to the ‘warning’ event:

The —trace-warnings command-line option can be used to have the default console output for warnings include the full stack trace of the warning.

Launching Node.js using the —throw-deprecation command-line flag will cause custom deprecation warnings to be thrown as exceptions.

Using the —trace-deprecation command-line flag will cause the custom deprecation to be printed to stderr along with the stack trace.

Using the —no-deprecation command-line flag will suppress all reporting of the custom deprecation.

The *-deprecation command-line flags only affect warnings that use the name ‘DeprecationWarning’ .

Event: ‘worker’ #

The ‘worker’ event is emitted after a new thread has been created.

Emitting custom warnings #

See the process.emitWarning() method for issuing custom or application-specific warnings.

Node.js warning names #

There are no strict guidelines for warning types (as identified by the name property) emitted by Node.js. New types of warnings can be added at any time. A few of the warning types that are most common include:

• ‘DeprecationWarning’ — Indicates use of a deprecated Node.js API or feature. Such warnings must include a ‘code’ property identifying the deprecation code.
• ‘ExperimentalWarning’ — Indicates use of an experimental Node.js API or feature. Such features must be used with caution as they may change at any time and are not subject to the same strict semantic-versioning and long-term support policies as supported features.
• ‘MaxListenersExceededWarning’ — Indicates that too many listeners for a given event have been registered on either an EventEmitter or EventTarget . This is often an indication of a memory leak.
• ‘TimeoutOverflowWarning’ — Indicates that a numeric value that cannot fit within a 32-bit signed integer has been provided to either the setTimeout() or setInterval() functions.
• ‘UnsupportedWarning’ — Indicates use of an unsupported option or feature that will be ignored rather than treated as an error. One example is use of the HTTP response status message when using the HTTP/2 compatibility API.

Signal events #

Signal events will be emitted when the Node.js process receives a signal. Please refer to signal(7) for a listing of standard POSIX signal names such as ‘SIGINT’ , ‘SIGHUP’ , etc.

Signals are not available on Worker threads.

The signal handler will receive the signal’s name ( ‘SIGINT’ , ‘SIGTERM’ , etc.) as the first argument.

The name of each event will be the uppercase common name for the signal (e.g. ‘SIGINT’ for SIGINT signals).

• ‘SIGUSR1’ is reserved by Node.js to start the debugger. It’s possible to install a listener but doing so might interfere with the debugger.
• ‘SIGTERM’ and ‘SIGINT’ have default handlers on non-Windows platforms that reset the terminal mode before exiting with code 128 + signal number . If one of these signals has a listener installed, its default behavior will be removed (Node.js will no longer exit).
• ‘SIGPIPE’ is ignored by default. It can have a listener installed.
• ‘SIGHUP’ is generated on Windows when the console window is closed, and on other platforms under various similar conditions. See signal(7) . It can have a listener installed, however Node.js will be unconditionally terminated by Windows about 10 seconds later. On non-Windows platforms, the default behavior of SIGHUP is to terminate Node.js, but once a listener has been installed its default behavior will be removed.
• ‘SIGTERM’ is not supported on Windows, it can be listened on.
• ‘SIGINT’ from the terminal is supported on all platforms, and can usually be generated with Ctrl + C (though this may be configurable). It is not generated when terminal raw mode is enabled and Ctrl + C is used.
• ‘SIGBREAK’ is delivered on Windows when Ctrl + Break is pressed. On non-Windows platforms, it can be listened on, but there is no way to send or generate it.
• ‘SIGWINCH’ is delivered when the console has been resized. On Windows, this will only happen on write to the console when the cursor is being moved, or when a readable tty is used in raw mode.
• ‘SIGKILL’ cannot have a listener installed, it will unconditionally terminate Node.js on all platforms.
• ‘SIGSTOP’ cannot have a listener installed.
• ‘SIGBUS’ , ‘SIGFPE’ , ‘SIGSEGV’ , and ‘SIGILL’ , when not raised artificially using kill(2) , inherently leave the process in a state from which it is not safe to call JS listeners. Doing so might cause the process to stop responding.
• 0 can be sent to test for the existence of a process, it has no effect if the process exists, but will throw an error if the process does not exist.

Windows does not support signals so has no equivalent to termination by signal, but Node.js offers some emulation with process.kill() , and subprocess.kill() :

• Sending SIGINT , SIGTERM , and SIGKILL will cause the unconditional termination of the target process, and afterwards, subprocess will report that the process was terminated by signal.
• Sending signal 0 can be used as a platform independent way to test for the existence of a process.

process.abort() #

The process.abort() method causes the Node.js process to exit immediately and generate a core file.

This feature is not available in Worker threads.

process.allowedNodeEnvironmentFlags #

The process.allowedNodeEnvironmentFlags property is a special, read-only Set of flags allowable within the NODE_OPTIONS environment variable.

process.allowedNodeEnvironmentFlags extends Set , but overrides Set.prototype.has to recognize several different possible flag representations. process.allowedNodeEnvironmentFlags.has() will return true in the following cases:

• Flags may omit leading single ( — ) or double ( — ) dashes; e.g., inspect-brk for —inspect-brk , or r for -r .
• Flags passed through to V8 (as listed in —v8-options ) may replace one or more non-leading dashes for an underscore, or vice-versa; e.g., —perf_basic_prof , —perf-basic-prof , —perf_basic-prof , etc.
• Flags may contain one or more equals ( = ) characters; all characters after and including the first equals will be ignored; e.g., —stack-trace-limit=100 .
• Flags must be allowable within NODE_OPTIONS .

When iterating over process.allowedNodeEnvironmentFlags , flags will appear only once; each will begin with one or more dashes. Flags passed through to V8 will contain underscores instead of non-leading dashes:

The methods add() , clear() , and delete() of process.allowedNodeEnvironmentFlags do nothing, and will fail silently.

If Node.js was compiled without NODE_OPTIONS support (shown in process.config ), process.allowedNodeEnvironmentFlags will contain what would have been allowable.

process.arch #

The operating system CPU architecture for which the Node.js binary was compiled. Possible values are: ‘arm’ , ‘arm64’ , ‘ia32’ , ‘mips’ , ‘mipsel’ , ‘ppc’ , ‘ppc64’ , ‘s390’ , ‘s390x’ , and ‘x64’ .

process.argv #

The process.argv property returns an array containing the command-line arguments passed when the Node.js process was launched. The first element will be process.execPath . See process.argv0 if access to the original value of argv[0] is needed. The second element will be the path to the JavaScript file being executed. The remaining elements will be any additional command-line arguments.

For example, assuming the following script for process-args.js :

Launching the Node.js process as:

Would generate the output:

process.argv0 #

The process.argv0 property stores a read-only copy of the original value of argv[0] passed when Node.js starts.

process.channel #

History

The object no longer accidentally exposes native C++ bindings.

If the Node.js process was spawned with an IPC channel (see the Child Process documentation), the process.channel property is a reference to the IPC channel. If no IPC channel exists, this property is undefined .

process.channel.ref() #

This method makes the IPC channel keep the event loop of the process running if .unref() has been called before.

Typically, this is managed through the number of ‘disconnect’ and ‘message’ listeners on the process object. However, this method can be used to explicitly request a specific behavior.

process.channel.unref() #

This method makes the IPC channel not keep the event loop of the process running, and lets it finish even while the channel is open.

Typically, this is managed through the number of ‘disconnect’ and ‘message’ listeners on the process object. However, this method can be used to explicitly request a specific behavior.

process.chdir(directory) #

The process.chdir() method changes the current working directory of the Node.js process or throws an exception if doing so fails (for instance, if the specified directory does not exist).

This feature is not available in Worker threads.

process.config #

History

The process.config object is now frozen.

Modifying process.config has been deprecated.

The process.config property returns a frozen Object containing the JavaScript representation of the configure options used to compile the current Node.js executable. This is the same as the config.gypi file that was produced when running the ./configure script.

An example of the possible output looks like:

process.connected #

If the Node.js process is spawned with an IPC channel (see the Child Process and Cluster documentation), the process.connected property will return true so long as the IPC channel is connected and will return false after process.disconnect() is called.

Once process.connected is false , it is no longer possible to send messages over the IPC channel using process.send() .

process.cpuUsage([previousValue]) #

• previousValue A previous return value from calling process.cpuUsage()
• Returns:
  • user
  • system

The process.cpuUsage() method returns the user and system CPU time usage of the current process, in an object with properties user and system , whose values are microsecond values (millionth of a second). These values measure time spent in user and system code respectively, and may end up being greater than actual elapsed time if multiple CPU cores are performing work for this process.

The result of a previous call to process.cpuUsage() can be passed as the argument to the function, to get a diff reading.

process.cwd() #

The process.cwd() method returns the current working directory of the Node.js process.

process.debugPort #

The port used by the Node.js debugger when enabled.

process.disconnect() #

If the Node.js process is spawned with an IPC channel (see the Child Process and Cluster documentation), the process.disconnect() method will close the IPC channel to the parent process, allowing the child process to exit gracefully once there are no other connections keeping it alive.

The effect of calling process.disconnect() is the same as calling ChildProcess.disconnect() from the parent process.

If the Node.js process was not spawned with an IPC channel, process.disconnect() will be undefined .

process.dlopen(module, filename[, flags]) #

History

Added support for the flags argument.

• module
• filename
• flags Default: os.constants.dlopen.RTLD_LAZY

The process.dlopen() method allows dynamically loading shared objects. It is primarily used by require() to load C++ Addons, and should not be used directly, except in special cases. In other words, require() should be preferred over process.dlopen() unless there are specific reasons such as custom dlopen flags or loading from ES modules.

The flags argument is an integer that allows to specify dlopen behavior. See the os.constants.dlopen documentation for details.

An important requirement when calling process.dlopen() is that the module instance must be passed. Functions exported by the C++ Addon are then accessible via module.exports .

The example below shows how to load a C++ Addon, named local.node , that exports a foo function. All the symbols are loaded before the call returns, by passing the RTLD_NOW constant. In this example the constant is assumed to be available.

process.emitWarning(warning[, options]) #

• warning | The warning to emit.
• options
  • type When warning is a String , type is the name to use for the type of warning being emitted. Default: ‘Warning’ .
  • code A unique identifier for the warning instance being emitted.
  • ctor When warning is a String , ctor is an optional function used to limit the generated stack trace. Default: process.emitWarning .
  • detail Additional text to include with the error.

The process.emitWarning() method can be used to emit custom or application specific process warnings. These can be listened for by adding a handler to the ‘warning’ event.

In this example, an Error object is generated internally by process.emitWarning() and passed through to the ‘warning’ handler.

If warning is passed as an Error object, the options argument is ignored.

process.emitWarning(warning[, type[, code]][, ctor]) #

• warning | The warning to emit.
• type When warning is a String , type is the name to use for the type of warning being emitted. Default: ‘Warning’ .
• code A unique identifier for the warning instance being emitted.
• ctor When warning is a String , ctor is an optional function used to limit the generated stack trace. Default: process.emitWarning .

The process.emitWarning() method can be used to emit custom or application specific process warnings. These can be listened for by adding a handler to the ‘warning’ event.

In each of the previous examples, an Error object is generated internally by process.emitWarning() and passed through to the ‘warning’ handler.

If warning is passed as an Error object, it will be passed through to the ‘warning’ event handler unmodified (and the optional type , code and ctor arguments will be ignored):

A TypeError is thrown if warning is anything other than a string or Error object.

While process warnings use Error objects, the process warning mechanism is not a replacement for normal error handling mechanisms.

The following additional handling is implemented if the warning type is ‘DeprecationWarning’ :

• If the —throw-deprecation command-line flag is used, the deprecation warning is thrown as an exception rather than being emitted as an event.
• If the —no-deprecation command-line flag is used, the deprecation warning is suppressed.
• If the —trace-deprecation command-line flag is used, the deprecation warning is printed to stderr along with the full stack trace.

Avoiding duplicate warnings #

As a best practice, warnings should be emitted only once per process. To do so, place the emitWarning() behind a boolean.

process.env #

History

Worker threads will now use a copy of the parent thread’s process.env by default, configurable through the env option of the Worker constructor.

Implicit conversion of variable value to string is deprecated.

The process.env property returns an object containing the user environment. See environ(7) .

An example of this object looks like:

It is possible to modify this object, but such modifications will not be reflected outside the Node.js process, or (unless explicitly requested) to other Worker threads. In other words, the following example would not work:

While the following will:

Assigning a property on process.env will implicitly convert the value to a string. This behavior is deprecated. Future versions of Node.js may throw an error when the value is not a string, number, or boolean.

Use delete to delete a property from process.env .

On Windows operating systems, environment variables are case-insensitive.

Unless explicitly specified when creating a Worker instance, each Worker thread has its own copy of process.env , based on its parent thread’s process.env , or whatever was specified as the env option to the Worker constructor. Changes to process.env will not be visible across Worker threads, and only the main thread can make changes that are visible to the operating system or to native add-ons.

process.execArgv #

The process.execArgv property returns the set of Node.js-specific command-line options passed when the Node.js process was launched. These options do not appear in the array returned by the process.argv property, and do not include the Node.js executable, the name of the script, or any options following the script name. These options are useful in order to spawn child processes with the same execution environment as the parent.

Results in process.execArgv :

Refer to Worker constructor for the detailed behavior of worker threads with this property.

process.execPath #

The process.execPath property returns the absolute pathname of the executable that started the Node.js process. Symbolic links, if any, are resolved.

process.exit([code]) #

• code The exit code. Default: 0 .

The process.exit() method instructs Node.js to terminate the process synchronously with an exit status of code . If code is omitted, exit uses either the ‘success’ code 0 or the value of process.exitCode if it has been set. Node.js will not terminate until all the ‘exit’ event listeners are called.

To exit with a ‘failure’ code:

The shell that executed Node.js should see the exit code as 1 .

Calling process.exit() will force the process to exit as quickly as possible even if there are still asynchronous operations pending that have not yet completed fully, including I/O operations to process.stdout and process.stderr .

In most situations, it is not actually necessary to call process.exit() explicitly. The Node.js process will exit on its own if there is no additional work pending in the event loop. The process.exitCode property can be set to tell the process which exit code to use when the process exits gracefully.

For instance, the following example illustrates a misuse of the process.exit() method that could lead to data printed to stdout being truncated and lost:

The reason this is problematic is because writes to process.stdout in Node.js are sometimes asynchronous and may occur over multiple ticks of the Node.js event loop. Calling process.exit() , however, forces the process to exit before those additional writes to stdout can be performed.

Rather than calling process.exit() directly, the code should set the process.exitCode and allow the process to exit naturally by avoiding scheduling any additional work for the event loop:

If it is necessary to terminate the Node.js process due to an error condition, throwing an uncaught error and allowing the process to terminate accordingly is safer than calling process.exit() .

In Worker threads, this function stops the current thread rather than the current process.

process.exitCode #

A number which will be the process exit code, when the process either exits gracefully, or is exited via process.exit() without specifying a code.

Specifying a code to process.exit(code) will override any previous setting of process.exitCode .

process.getActiveResourcesInfo() #

The process.getActiveResourcesInfo() method returns an array of strings containing the types of the active resources that are currently keeping the event loop alive.

process.getegid() #

The process.getegid() method returns the numerical effective group identity of the Node.js process. (See getegid(2) .)

This function is only available on POSIX platforms (i.e. not Windows or Android).

process.geteuid() #

The process.geteuid() method returns the numerical effective user identity of the process. (See geteuid(2) .)

This function is only available on POSIX platforms (i.e. not Windows or Android).

process.getgid() #

The process.getgid() method returns the numerical group identity of the process. (See getgid(2) .)

This function is only available on POSIX platforms (i.e. not Windows or Android).

process.getgroups() #

The process.getgroups() method returns an array with the supplementary group IDs. POSIX leaves it unspecified if the effective group ID is included but Node.js ensures it always is.

This function is only available on POSIX platforms (i.e. not Windows or Android).

process.getuid() #

The process.getuid() method returns the numeric user identity of the process. (See getuid(2) .)

This function is only available on POSIX platforms (i.e. not Windows or Android).

process.hasUncaughtExceptionCaptureCallback() #

Indicates whether a callback has been set using process.setUncaughtExceptionCaptureCallback() .

process.hrtime([time]) #

• time The result of a previous call to process.hrtime()
• Returns:

This is the legacy version of process.hrtime.bigint() before bigint was introduced in JavaScript.

The process.hrtime() method returns the current high-resolution real time in a [seconds, nanoseconds] tuple Array , where nanoseconds is the remaining part of the real time that can’t be represented in second precision.

time is an optional parameter that must be the result of a previous process.hrtime() call to diff with the current time. If the parameter passed in is not a tuple Array , a TypeError will be thrown. Passing in a user-defined array instead of the result of a previous call to process.hrtime() will lead to undefined behavior.

These times are relative to an arbitrary time in the past, and not related to the time of day and therefore not subject to clock drift. The primary use is for measuring performance between intervals:

process.hrtime.bigint() #

The bigint version of the process.hrtime() method returning the current high-resolution real time in nanoseconds as a bigint .

Unlike process.hrtime() , it does not support an additional time argument since the difference can just be computed directly by subtraction of the two bigint s.

• user | The user name or numeric identifier.
• extraGroup | A group name or numeric identifier.

The process.initgroups() method reads the /etc/group file and initializes the group access list, using all groups of which the user is a member. This is a privileged operation that requires that the Node.js process either have root access or the CAP_SETGID capability.

Use care when dropping privileges:

This function is only available on POSIX platforms (i.e. not Windows or Android). This feature is not available in Worker threads.

process.kill(pid[, signal]) #

• pid A process ID
• signal | The signal to send, either as a string or number. Default: ‘SIGTERM’ .

The process.kill() method sends the signal to the process identified by pid .

Signal names are strings such as ‘SIGINT’ or ‘SIGHUP’ . See Signal Events and kill(2) for more information.

This method will throw an error if the target pid does not exist. As a special case, a signal of 0 can be used to test for the existence of a process. Windows platforms will throw an error if the pid is used to kill a process group.

Even though the name of this function is process.kill() , it is really just a signal sender, like the kill system call. The signal sent may do something other than kill the target process.

When SIGUSR1 is received by a Node.js process, Node.js will start the debugger. See Signal Events.

process.mainModule #

The process.mainModule property provides an alternative way of retrieving require.main . The difference is that if the main module changes at runtime, require.main may still refer to the original main module in modules that were required before the change occurred. Generally, it’s safe to assume that the two refer to the same module.

As with require.main , process.mainModule will be undefined if there is no entry script.

process.memoryUsage() #

History

Added arrayBuffers to the returned object.

Added external to the returned object.

• Returns:
  • rss
  • heapTotal
  • heapUsed
  • external
  • arrayBuffers

Returns an object describing the memory usage of the Node.js process measured in bytes.

• heapTotal and heapUsed refer to V8’s memory usage.
• external refers to the memory usage of C++ objects bound to JavaScript objects managed by V8.
• rss , Resident Set Size, is the amount of space occupied in the main memory device (that is a subset of the total allocated memory) for the process, including all C++ and JavaScript objects and code.
• arrayBuffers refers to memory allocated for ArrayBuffer s and SharedArrayBuffer s, including all Node.js Buffer s. This is also included in the external value. When Node.js is used as an embedded library, this value may be 0 because allocations for ArrayBuffer s may not be tracked in that case.

When using Worker threads, rss will be a value that is valid for the entire process, while the other fields will only refer to the current thread.

The process.memoryUsage() method iterates over each page to gather information about memory usage which might be slow depending on the program memory allocations.

The process.memoryUsage.rss() method returns an integer representing the Resident Set Size (RSS) in bytes.

The Resident Set Size, is the amount of space occupied in the main memory device (that is a subset of the total allocated memory) for the process, including all C++ and JavaScript objects and code.

This is the same value as the rss property provided by process.memoryUsage() but process.memoryUsage.rss() is faster.

process.nextTick(callback[, . args]) #

History

Passing an invalid callback to the callback argument now throws ERR_INVALID_ARG_TYPE instead of ERR_INVALID_CALLBACK .

Additional arguments after callback are now supported.

process.nextTick() adds callback to the «next tick queue». This queue is fully drained after the current operation on the JavaScript stack runs to completion and before the event loop is allowed to continue. It’s possible to create an infinite loop if one were to recursively call process.nextTick() . See the Event Loop guide for more background.

This is important when developing APIs in order to give users the opportunity to assign event handlers after an object has been constructed but before any I/O has occurred:

It is very important for APIs to be either 100% synchronous or 100% asynchronous. Consider this example:

This API is hazardous because in the following case:

It is not clear whether foo() or bar() will be called first.

The following approach is much better:

When to use queueMicrotask() vs. process.nextTick() #

The queueMicrotask() API is an alternative to process.nextTick() that also defers execution of a function using the same microtask queue used to execute the then, catch, and finally handlers of resolved promises. Within Node.js, every time the «next tick queue» is drained, the microtask queue is drained immediately after.

For most userland use cases, the queueMicrotask() API provides a portable and reliable mechanism for deferring execution that works across multiple JavaScript platform environments and should be favored over process.nextTick() . In simple scenarios, queueMicrotask() can be a drop-in replacement for process.nextTick() .

One note-worthy difference between the two APIs is that process.nextTick() allows specifying additional values that will be passed as arguments to the deferred function when it is called. Achieving the same result with queueMicrotask() requires using either a closure or a bound function:

There are minor differences in the way errors raised from within the next tick queue and microtask queue are handled. Errors thrown within a queued microtask callback should be handled within the queued callback when possible. If they are not, the process.on(‘uncaughtException’) event handler can be used to capture and handle the errors.

When in doubt, unless the specific capabilities of process.nextTick() are needed, use queueMicrotask() .

process.noDeprecation #

The process.noDeprecation property indicates whether the —no-deprecation flag is set on the current Node.js process. See the documentation for the ‘warning’ event and the emitWarning() method for more information about this flag’s behavior.

process.pid #

The process.pid property returns the PID of the process.

process.platform #

The process.platform property returns a string identifying the operating system platform for which the Node.js binary was compiled.

Currently possible values are:

The value ‘android’ may also be returned if the Node.js is built on the Android operating system. However, Android support in Node.js is experimental.

process.ppid #

The process.ppid property returns the PID of the parent of the current process.

process.release #

History

The lts property is now supported.

The process.release property returns an Object containing metadata related to the current release, including URLs for the source tarball and headers-only tarball.

process.release contains the following properties:

• name A value that will always be ‘node’ .
• sourceUrl an absolute URL pointing to a .tar.gz file containing the source code of the current release.
• headersUrl an absolute URL pointing to a .tar.gz file containing only the source header files for the current release. This file is significantly smaller than the full source file and can be used for compiling Node.js native add-ons.
• libUrl | an absolute URL pointing to a node.lib file matching the architecture and version of the current release. This file is used for compiling Node.js native add-ons. This property is only present on Windows builds of Node.js and will be missing on all other platforms.
• lts | a string label identifying the LTS label for this release. This property only exists for LTS releases and is undefined for all other release types, including Current releases. Valid values include the LTS Release code names (including those that are no longer supported).
  • ‘Fermium’ for the 14.x LTS line beginning with 14.15.0.
  • ‘Gallium’ for the 16.x LTS line beginning with 16.13.0.
  • ‘Hydrogen’ for the 18.x LTS line beginning with 18.12.0. For other LTS Release code names, see Node.js Changelog Archive

In custom builds from non-release versions of the source tree, only the name property may be present. The additional properties should not be relied upon to exist.

process.report #

History

This API is no longer experimental.

process.report is an object whose methods are used to generate diagnostic reports for the current process. Additional documentation is available in the report documentation.

process.report.compact #

Write reports in a compact format, single-line JSON, more easily consumable by log processing systems than the default multi-line format designed for human consumption.

process.report.directory #

History

This API is no longer experimental.

Added in: v11.12.0

Directory where the report is written. The default value is the empty string, indicating that reports are written to the current working directory of the Node.js process.

process.report.filename #

History

This API is no longer experimental.

Added in: v11.12.0

Filename where the report is written. If set to the empty string, the output filename will be comprised of a timestamp, PID, and sequence number. The default value is the empty string.

If the value of process.report.filename is set to ‘stdout’ or ‘stderr’ , the report is written to the stdout or stderr of the process respectively.

process.report.getReport([err]) #

History

This API is no longer experimental.

• err A custom error used for reporting the JavaScript stack.
• Returns:

Returns a JavaScript Object representation of a diagnostic report for the running process. The report’s JavaScript stack trace is taken from err , if present.

Additional documentation is available in the report documentation.

process.report.reportOnFatalError #

History

This API is no longer experimental.

Added in: v11.12.0

If true , a diagnostic report is generated on fatal errors, such as out of memory errors or failed C++ assertions.

process.report.reportOnSignal #

History

This API is no longer experimental.

Added in: v11.12.0

If true , a diagnostic report is generated when the process receives the signal specified by process.report.signal .

process.report.reportOnUncaughtException #

History

This API is no longer experimental.

Added in: v11.12.0

If true , a diagnostic report is generated on uncaught exception.

process.report.signal #

History

This API is no longer experimental.

Added in: v11.12.0

The signal used to trigger the creation of a diagnostic report. Defaults to ‘SIGUSR2’ .

process.report.writeReport([filename][, err]) #

History

This API is no longer experimental.

filename Name of the file where the report is written. This should be a relative path, that will be appended to the directory specified in process.report.directory , or the current working directory of the Node.js process, if unspecified.

err A custom error used for reporting the JavaScript stack.

Returns: Returns the filename of the generated report.

Writes a diagnostic report to a file. If filename is not provided, the default filename includes the date, time, PID, and a sequence number. The report’s JavaScript stack trace is taken from err , if present.

If the value of filename is set to ‘stdout’ or ‘stderr’ , the report is written to the stdout or stderr of the process respectively.

Additional documentation is available in the report documentation.

process.resourceUsage() #

• Returns: the resource usage for the current process. All of these values come from the uv_getrusage call which returns a uv_rusage_t struct.
  • userCPUTime maps to ru_utime computed in microseconds. It is the same value as process.cpuUsage().user .
  • systemCPUTime maps to ru_stime computed in microseconds. It is the same value as process.cpuUsage().system .
  • maxRSS maps to ru_maxrss which is the maximum resident set size used in kilobytes.
  • sharedMemorySize maps to ru_ixrss but is not supported by any platform.
  • unsharedDataSize maps to ru_idrss but is not supported by any platform.
  • unsharedStackSize maps to ru_isrss but is not supported by any platform.
  • minorPageFault maps to ru_minflt which is the number of minor page faults for the process, see this article for more details.
  • majorPageFault maps to ru_majflt which is the number of major page faults for the process, see this article for more details. This field is not supported on Windows.
  • swappedOut maps to ru_nswap but is not supported by any platform.
  • fsRead maps to ru_inblock which is the number of times the file system had to perform input.
  • fsWrite maps to ru_oublock which is the number of times the file system had to perform output.
  • ipcSent maps to ru_msgsnd but is not supported by any platform.
  • ipcReceived maps to ru_msgrcv but is not supported by any platform.
  • signalsCount maps to ru_nsignals but is not supported by any platform.
  • voluntaryContextSwitches maps to ru_nvcsw which is the number of times a CPU context switch resulted due to a process voluntarily giving up the processor before its time slice was completed (usually to await availability of a resource). This field is not supported on Windows.
  • involuntaryContextSwitches maps to ru_nivcsw which is the number of times a CPU context switch resulted due to a higher priority process becoming runnable or because the current process exceeded its time slice. This field is not supported on Windows.

process.send(message[, sendHandle[, options]][, callback]) #

• message
• sendHandle |
• options used to parameterize the sending of certain types of handles. options supports the following properties:
  • keepOpen A value that can be used when passing instances of net.Socket . When true , the socket is kept open in the sending process. Default: false .
• callback
• Returns:

If Node.js is spawned with an IPC channel, the process.send() method can be used to send messages to the parent process. Messages will be received as a ‘message’ event on the parent’s ChildProcess object.

If Node.js was not spawned with an IPC channel, process.send will be undefined .

The message goes through serialization and parsing. The resulting message might not be the same as what is originally sent.

process.setegid(id) #

The process.setegid() method sets the effective group identity of the process. (See setegid(2) .) The id can be passed as either a numeric ID or a group name string. If a group name is specified, this method blocks while resolving the associated a numeric ID.

This function is only available on POSIX platforms (i.e. not Windows or Android). This feature is not available in Worker threads.

process.seteuid(id) #

The process.seteuid() method sets the effective user identity of the process. (See seteuid(2) .) The id can be passed as either a numeric ID or a username string. If a username is specified, the method blocks while resolving the associated numeric ID.

This function is only available on POSIX platforms (i.e. not Windows or Android). This feature is not available in Worker threads.

process.setgid(id) #

The process.setgid() method sets the group identity of the process. (See setgid(2) .) The id can be passed as either a numeric ID or a group name string. If a group name is specified, this method blocks while resolving the associated numeric ID.

This function is only available on POSIX platforms (i.e. not Windows or Android). This feature is not available in Worker threads.

process.setgroups(groups) #

The process.setgroups() method sets the supplementary group IDs for the Node.js process. This is a privileged operation that requires the Node.js process to have root or the CAP_SETGID capability.

The groups array can contain numeric group IDs, group names, or both.

This function is only available on POSIX platforms (i.e. not Windows or Android). This feature is not available in Worker threads.

process.setuid(id) #

The process.setuid(id) method sets the user identity of the process. (See setuid(2) .) The id can be passed as either a numeric ID or a username string. If a username is specified, the method blocks while resolving the associated numeric ID.

This function is only available on POSIX platforms (i.e. not Windows or Android). This feature is not available in Worker threads.

process.setSourceMapsEnabled(val) #

This function enables or disables the Source Map v3 support for stack traces.

It provides same features as launching Node.js process with commandline options —enable-source-maps .

Only source maps in JavaScript files that are loaded after source maps has been enabled will be parsed and loaded.

process.setUncaughtExceptionCaptureCallback(fn) #

The process.setUncaughtExceptionCaptureCallback() function sets a function that will be invoked when an uncaught exception occurs, which will receive the exception value itself as its first argument.

If such a function is set, the ‘uncaughtException’ event will not be emitted. If —abort-on-uncaught-exception was passed from the command line or set through v8.setFlagsFromString() , the process will not abort. Actions configured to take place on exceptions such as report generations will be affected too

To unset the capture function, process.setUncaughtExceptionCaptureCallback(null) may be used. Calling this method with a non- null argument while another capture function is set will throw an error.

Using this function is mutually exclusive with using the deprecated domain built-in module.

process.stderr #

The process.stderr property returns a stream connected to stderr (fd 2 ). It is a net.Socket (which is a Duplex stream) unless fd 2 refers to a file, in which case it is a Writable stream.

process.stderr differs from other Node.js streams in important ways. See note on process I/O for more information.

process.stderr.fd #

This property refers to the value of underlying file descriptor of process.stderr . The value is fixed at 2 . In Worker threads, this field does not exist.

process.stdin #

The process.stdin property returns a stream connected to stdin (fd 0 ). It is a net.Socket (which is a Duplex stream) unless fd 0 refers to a file, in which case it is a Readable stream.

For details of how to read from stdin see readable.read() .

As a Duplex stream, process.stdin can also be used in «old» mode that is compatible with scripts written for Node.js prior to v0.10. For more information see Stream compatibility.

In «old» streams mode the stdin stream is paused by default, so one must call process.stdin.resume() to read from it. Note also that calling process.stdin.resume() itself would switch stream to «old» mode.

process.stdin.fd #

This property refers to the value of underlying file descriptor of process.stdin . The value is fixed at 0 . In Worker threads, this field does not exist.

process.stdout #

The process.stdout property returns a stream connected to stdout (fd 1 ). It is a net.Socket (which is a Duplex stream) unless fd 1 refers to a file, in which case it is a Writable stream.

For example, to copy process.stdin to process.stdout :

process.stdout differs from other Node.js streams in important ways. See note on process I/O for more information.

process.stdout.fd #

This property refers to the value of underlying file descriptor of process.stdout . The value is fixed at 1 . In Worker threads, this field does not exist.

A note on process I/O #

process.stdout and process.stderr differ from other Node.js streams in important ways:

1. They are used internally by console.log() and console.error() , respectively.
2. Writes may be synchronous depending on what the stream is connected to and whether the system is Windows or POSIX:
   • Files: synchronous on Windows and POSIX
   • TTYs (Terminals): asynchronous on Windows, synchronous on POSIX
   • Pipes (and sockets): synchronous on Windows, asynchronous on POSIX

These behaviors are partly for historical reasons, as changing them would create backward incompatibility, but they are also expected by some users.

Synchronous writes avoid problems such as output written with console.log() or console.error() being unexpectedly interleaved, or not written at all if process.exit() is called before an asynchronous write completes. See process.exit() for more information.

Warning: Synchronous writes block the event loop until the write has completed. This can be near instantaneous in the case of output to a file, but under high system load, pipes that are not being read at the receiving end, or with slow terminals or file systems, it’s possible for the event loop to be blocked often enough and long enough to have severe negative performance impacts. This may not be a problem when writing to an interactive terminal session, but consider this particularly careful when doing production logging to the process output streams.

To check if a stream is connected to a TTY context, check the isTTY property.

See the TTY documentation for more information.

Источник

Adblock
detector