event-loop-lag - npm Package Compare versions

Comparing version 1.0.3 to 1.1.0

event-loop-lag.js

@@ -28,5 +28,11 @@
     // how much time has actually elapsed in the loop beyond what
-    // setTimeout says is supposed to happen
+    // setTimeout says is supposed to happen. we use setTimeout to
+    // cover multiple iterations of the event loop, getting a larger
+    // sample of what the process is working on.
     var t = time();
-    delay = t - start - ms;
+
+    // we use Math.max to handle case where timers are running efficiently
+    // and our callback executes earlier than `ms` due to how timers are
+    // implemented. this is ok. it means we're healthy.
+    delay = Math.max(0, t - start - ms);
     start = t;
@@ -33,0 +39,0 @@

History.md

 
+1.1.0 / 2015-02-18
+==================
+
+ * fixed; report healthy event loops as 0
+ * test; remove --harmony-generators flag
+
 1.0.3 / 2015-01-06
@@ -3,0 +9,0 @@ ==================

package.json

 {
   "name": "event-loop-lag",
-  "version": "1.0.3",
+  "version": "1.1.0",
   "description": "Measure event loop lag",
@@ -5,0 +5,0 @@ "main": "event-loop-lag.js",

New alerts

New author

Supply chain risk

A new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.

Found 1 instance in 1 package

Improved metrics

Total package byte prevSize

7595

increased by10.62%

Number of package files

12

increased by9.09%

Lines of code

109

increased by21.11%

Worsened metrics

Number of medium supply chain risk alerts

2

increased by100%

No dependency changes