wtfnode - npm Package Compare versions

Comparing version 0.3.5 to 0.4.0

index.js

@@ -1,4 +0,3 @@
-#!/usr/bin/env node
+'use strict';
 
-'use strict';
 // Don't require these until we've hooked certain builtins
@@ -445,3 +444,3 @@ var ChildProcess,
     // the module that it is the 'main' module.
-    var newArgv = parseArgs(process.argv)
+    var newArgv = parseArgs(process.argv);
     var Module = require('module');
@@ -448,0 +447,0 @@ process.argv = newArgv;

package.json

 {
   "name": "wtfnode",
-  "version": "0.3.5",
+  "version": "0.4.0",
   "description": "Utility to help find out why Node isn't exiting",
@@ -15,5 +15,5 @@ "repository": {
   "bin": {
-    "wtfnode": "index.js"
+    "wtfnode": "proxy.js"
   },
   "license": "ISC"
 }

README.md

@@ -43,2 +43,4 @@ # What?
 
+Version 0.4.0: When a module has bound SIGINT, Node will no longer be able to exit when in an infinite loop. `wtfnode` now instead launches the target by way of a watchdog proxy; you may now Ctrl+C twice to force termination. No information will be available, since no other code can be run while an infinite loop is executing, but this should at least make life a little easier.
+
 # Module usage
@@ -45,0 +47,0 @@

New alerts

Environment variable access

Supply chain risk

Package accesses environment variables, which may be a sign of credential stuffing or data theft.

Found 1 instance in 1 package

Improved metrics

Total package byte prevSize

26474

increased by3.95%

Number of package files

9

increased by12.5%

Lines of code

517

increased by3.4%

Number of lines in readme file

64

increased by3.23%

Worsened metrics

Number of low supply chain risk alerts

3

increased by50%

Number of medium supply chain risk alerts

15

increased by7.14%

No dependency changes