log-process-errors

Breaking changes

• Minimal supported Node.js version is now 18.18.0

Dependencies

• Upgrade internal dependencies

Breaking changes

• Minimal supported Node.js version is now 16.17.0

Features

• Improve tree-shaking support

Internal

• Add more tests

Features

• Improve error detection using is-error-instance

Package size

The npm package size has been reduced by 98%, from 4500kB to 87kB.

Custom logic

The log option was renamed to onError. Its arguments are (originalError, event) instead of (error, level, originalError).

The process error event is now passed as a second argument instead of being set as error.name. Its case is not capitalized anymore, to match the event name in Node.js.

Before:

logProcessErrors({
  log(error) {
    if (error.name === 'UncaughtException') {
      console.error(error)
    }
  },
})

After:

logProcessErrors({
  onError(error, event) {
    if (event === 'uncaughtException') {
      console.error(error)
    }
  },
})

Pretty-printing

Errors are not pretty-printed anymore. As a consequence, the colors option was removed too. The onError option can be used instead to customize how the errors are printed.

Filtering

The levels option was removed. The onError option can be used for filtering.

Before:

logProcessErrors({
  levels: {
    warning: 'silent',
  },
})

After:

logProcessErrors({
  onError(error, event) {
    if (event !== 'warning') {
      console.error(error)
    }
  },
})

Testing option

The testing option was removed. The onError option can be used instead.

Before:

logProcessErrors({ testing: 'ava' })

After:

logProcessErrors({
  // Throw the `error` to make the unit test fail while letting other tests run
  onError(error) {
    throw error
  },
})

Process exit

The exitOn option was changed from an array of strings to a simpler boolean. It was also renamed exit.

The exit is still graceful, i.e. it waits for ongoing tasks to complete, up to 3 seconds. However, if there are none, the process now exits immediately.

Before:

logProcessErrors({ exitOn: [] })

After:

logProcessErrors({ exit: false })

Compatibility with other libraries

If other libraries (such as Winston, Bugsnag, etc.) are also listening for process events, they might also try to exit the process. This created conflicts with this library. This has been fixed by making the exit option default to false when process events listeners already exist.

Bug fixes

• Fix support for --unhandled-rejections=strict
• Do not crash when error.stack is undefined or null
• Support cross-realm errors

TypeScript

TypeScript types have been simplified.

Internal

Added 100% test coverage.

Features

• Reduce npm package size

Documentation

• Document related projects, including modern-errors

Features

• Reduce npm package size

Features

• Add TypeScript types

Breaking changes

• Minimal supported Node.js version is now 14.18.0

Breaking changes

• multipleResolves has been deprecated by Node.js. Therefore, support for it has been removed.
  • If your code uses the level or exitOn option with a multipleResolves parameter, you should remove it.
  • Otherwise, this release is not a breaking change for you.

Bug fixes

• Fix main field in package.json

Breaking changes

• The log-process-errors/build/register export has been removed. Please import log-process-errors directly instead.
• The testing option value node-tap has been renamed to node_tap
• Minimal supported Node.js version is now 12.20.0
• This package is now an ES module. It can only be loaded with an import or import() statement, not require(). See this post for more information.

Features

• Improve colors detection

Features

• Improve colors on Windows terminal

Features

• The exitOn() option now defaults to ['uncaughtException', 'unhandledRejection'] on Node >= 15.0.0. Its default
  value is still ['uncaughtException'] on Node < 15.0.0. This is to mimic Node.js default behavior: since Node 15.0.0, processes exit on unhandled promises.

Dependency

• Remove unused dependency core-js

Bug fixes

• Fix handling uncaught exceptions or warnings that are not Error instances (#32)

Bug fixes

• Fix handling uncaught exceptions or warnings that are not Error instances (#32)