Question 1

What's the difference between hard-rejection and loud-rejection?

Accepted Answer

hard-rejection is designed for long-running processes like servers and exits the process on unhandled rejections, while loud-rejection is for command-line apps and tests and logs errors without terminating. Choose based on whether you need the process to crash or just log.

Question 2

How do I use hard-rejection with ES6 imports?

Accepted Answer

You can import 'hard-rejection/register' in your ES6 module to automatically install the handler. This is shown in the README's register script example for simplified setup.

Question 3

Does hard-rejection work with Node.js 14?

Accepted Answer

Yes, hard-rejection is compatible with Node.js 14 and earlier versions where unhandled rejections are silent by default. It's specifically useful for environments before Node.js 15.

Question 4

Can I change how errors are logged with hard-rejection?

Accepted Answer

Yes, you can pass a custom logging function to the hardRejection() call to print error stacks in a specific way before the process exits, as documented in the API section.

Question 5

Is hard-rejection deprecated since Node.js 15?

Accepted Answer

For Node.js 15 and later, hard-rejection is moot because the native behavior already throws on unhandled rejections. However, it's still useful for projects stuck on older Node.js versions or for enforcing a specific fail-fast policy.

Question 6

When should I avoid using hard-rejection?

Accepted Answer

Avoid using hard-rejection in reusable modules or libraries, as it will crash dependent applications. Also, if you're on Node.js 15+, it's redundant since the default handling is similar.

hard-rejection

What is hard-rejection?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions