EroticDungeonGame/node_modules/signal-exit
3944Realms 8c4ce2709c fix(兼容emotescraft和rideeverything): 修改骑乘逻辑和tick取消EmtoesCraft表情
使用Mixin中检测绕过骑乘取消和开始骑乘逻辑,避免原版的unRide方法导致非预期的退出设备;在每tick检测,如果在设备上则停止表情动画
2026-02-20 14:45:57 +08:00
..
index.js fix(兼容emotescraft和rideeverything): 修改骑乘逻辑和tick取消EmtoesCraft表情 2026-02-20 14:45:57 +08:00
LICENSE.txt fix(兼容emotescraft和rideeverything): 修改骑乘逻辑和tick取消EmtoesCraft表情 2026-02-20 14:45:57 +08:00
package.json fix(兼容emotescraft和rideeverything): 修改骑乘逻辑和tick取消EmtoesCraft表情 2026-02-20 14:45:57 +08:00
README.md fix(兼容emotescraft和rideeverything): 修改骑乘逻辑和tick取消EmtoesCraft表情 2026-02-20 14:45:57 +08:00
signals.js fix(兼容emotescraft和rideeverything): 修改骑乘逻辑和tick取消EmtoesCraft表情 2026-02-20 14:45:57 +08:00

signal-exit

Build Status Coverage NPM version Standard Version

When you want to fire an event no matter how a process exits:

  • reaching the end of execution.
  • explicitly having process.exit(code) called.
  • having process.kill(pid, sig) called.
  • receiving a fatal signal from outside the process

Use signal-exit.

var onExit = require('signal-exit')

onExit(function (code, signal) {
  console.log('process exited!')
})

API

var remove = onExit(function (code, signal) {}, options)

The return value of the function is a function that will remove the handler.

Note that the function only fires for signals if the signal would cause the process to exit. That is, there are no other listeners, and it is a fatal signal.

Options

  • alwaysLast: Run this handler after any other signal or exit handlers. This causes process.emit to be monkeypatched.