FM / mjs

/usr/lib/node_modules/pnpm/dist/node_modules/signal-exit/dist/mjs/

/usr/lib/node_modules/pnpm/dist/node_modules/signal-exit/dist/mjs

Name	Size	Mode	Actions
browser.d.ts.map	349	0644	edit dl rm
browser.js	138	0644	edit dl rm
browser.js.map	668	0644	edit dl rm
index.d.ts.map	460	0644	edit dl rm
index.js	9090	0644	edit dl rm
index.js.map	17592	0644	edit dl rm
package.json	23	0644	edit dl rm
signals.d.ts.map	196	0644	edit dl rm
signals.js	1438	0644	edit dl rm
signals.js.map	2098	0644	edit dl rm

Edit: /usr/lib/node_modules/pnpm/dist/node_modules/signal-exit/dist/mjs/signals.js (1438B)

/**
 * This is not the set of all possible signals.
 *
 * It IS, however, the set of all signals that trigger
 * an exit on either Linux or BSD systems.  Linux is a
 * superset of the signal names supported on BSD, and
 * the unknown signals just fail to register, so we can
 * catch that easily enough.
 *
 * Windows signals are a different set, since there are
 * signals that terminate Windows processes, but don't
 * terminate (or don't even exist) on Posix systems.
 *
 * Don't bother with SIGKILL.  It's uncatchable, which
 * means that we can't fire any callbacks anyway.
 *
 * If a user does happen to register a handler on a non-
 * fatal signal like SIGWINCH or something, and then
 * exit, it'll end up firing `process.emit('exit')`, so
 * the handler will be fired anyway.
 *
 * SIGBUS, SIGFPE, SIGSEGV and SIGILL, when not raised
 * artificially, inherently leave the process in a
 * state from which it is not safe to try and enter JS
 * listeners.
 */
export const signals = [];
signals.push('SIGHUP', 'SIGINT', 'SIGTERM');
if (process.platform !== 'win32') {
    signals.push('SIGALRM', 'SIGABRT', 'SIGVTALRM', 'SIGXCPU', 'SIGXFSZ', 'SIGUSR2', 'SIGTRAP', 'SIGSYS', 'SIGQUIT', 'SIGIOT'
    // should detect profiler and enable/disable accordingly.
    // see #21
    // 'SIGPROF'
    );
}
if (process.platform === 'linux') {
    signals.push('SIGIO', 'SIGPOLL', 'SIGPWR', 'SIGSTKFLT');
}
//# sourceMappingURL=signals.js.map

cmd: