why-is-node-running - npm Package Compare versions

Comparing version 2.1.2 to 2.2.0

include.js

 var why = require('./')
 
-process.on('SIGUSR1', function() { why() })
+require('siginfo')(why, true)

package.json

 {
   "name": "why-is-node-running",
-  "version": "2.1.2",
+  "version": "2.2.0",
   "description": "Node is running but you don't know why? why-is-node-running is here to help you.",
   "main": "index.js",
   "dependencies": {
+    "siginfo": "^2.0.0",
     "stackback": "0.0.2"
@@ -8,0 +9,0 @@ },

README.md

@@ -75,3 +75,3 @@ # why-is-node-running
 
-You can also run `why-is-node-running` as a standalone if you don't want to include it inside your code. Sending `SIGUSR1` signal to the process will produce the log.
+You can also run `why-is-node-running` as a standalone if you don't want to include it inside your code. Sending `SIGUSR1`/`SIGINFO` signal to the process will produce the log. (`Ctrl + T` on macOS and BSD systems)
 
@@ -93,4 +93,14 @@ ```bash
 
+## Require CLI Option
+
+You can also use the node `-r` option to include `why-is-node-running`:
+
+```bash
+node -r why-is-node-running/include /path/to/some/file.js
+```
+
+The steps are otherwise the same as the above CLI section
+
 ## License
 
 MIT

New alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Fixed alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Improved metrics

Total package byte prevSize

7179

increased by4.13%

Number of lines in readme file

105

increased by10.53%

Worsened metrics

Dependency count

2

increased by100%

Dependency changes

• + Addedsiginfo@^2.0.0

• + Addedsiginfo@2.0.0(transitive)