
Research
SANDWORM_MODE: Shai-Hulud-Style npm Worm Hijacks CI Workflows and Poisons AI Toolchains
An emerging npm supply chain attack that infects repos, steals CI secrets, and targets developer AI toolchains for further compromise.
@dotcom-reliability-kit/crash-handler
Advanced tools
A method to bind an uncaught exception handler to ensure that fatal application errors are logged
A method to bind an uncaught exception handler to ensure that fatal application errors are logged. It is a replacement for Sentry fatal error logging. This module is part of FT.com Reliability Kit.
Install @dotcom-reliability-kit/crash-handler as a dependency:
npm install --save @dotcom-reliability-kit/crash-handler
Include in your code:
import registerCrashHandler from '@dotcom-reliability-kit/crash-handler';
// or
const registerCrashHandler = require('@dotcom-reliability-kit/crash-handler');
registerCrashHandlerThe registerCrashHandler function can be used to bind an event handler to the Node.js process.uncaughtException event. This ensures that your application logs a final message before crashing in the event on an unexpected error or promise rejection.
This function should only ever be called once in your app, normally alongside all your setup code (e.g. alongside creating an Express app).
[!TIP]
It's not a requirement, but generally the earlier the better with registering an uncaught exception handler – the sooner you register it the more likely you are to catch uncaught exceptions.
registerCrashHandler();
If an error is thrown which will crash your application, error information will be logged and then the process will exit with the value of process.exitCode or 1.
Config options can be passed into the registerCrashHandler function as an object with any of the keys below.
registerCrashHandler({
// Config options go here
});
options.loggerA logger object which implements two methods, error and warn, which have the following permissive signature:
type LogMethod = (...logData: any) => any;
This is passed directly onto the relevant log-error method, see the documentation for that package for more details.
options.processThe Node.js Process object to bind the error handling event to. You may use this if you are using a child process or want to mock the process object in your tests.
registerCrashHandler({
process: myProcessObject
});
The Reliability Kit crash handler is a replacement for Sentry's uncaught exception handling, which your app is likely to be using. You'll need to migrate away from Sentry in order to use this module. We maintain a migration guide for this on Confluence.
Consult the Migration Guide if you're trying to migrate to a later major version of this package.
See the central contributing guide for Reliability Kit.
Licensed under the MIT license.
Copyright © 2022, The Financial Times Ltd.
FAQs
A method to bind an uncaught exception handler to ensure that fatal application errors are logged
We found that @dotcom-reliability-kit/crash-handler demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 5 open source maintainers collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Research
An emerging npm supply chain attack that infects repos, steals CI secrets, and targets developer AI toolchains for further compromise.

Company News
Socket is proud to join the OpenJS Foundation as a Silver Member, deepening our commitment to the long-term health and security of the JavaScript ecosystem.

Security News
npm now links to Socket's security analysis on every package page. Here's what you'll find when you click through.