safe-timers
Advanced tools
Comparing version 1.0.0 to 1.0.1
{ | ||
"name": "safe-timers", | ||
"version": "1.0.0", | ||
"version": "1.0.1", | ||
"description": "Timers with near-infinite duration support", | ||
@@ -14,3 +14,3 @@ "main": "index.js", | ||
"type": "git", | ||
"url": "git+https://github.com/wizcorp/safe-timers.git" | ||
"url": "git+https://github.com/Wizcorp/safe-timers.git" | ||
}, | ||
@@ -28,5 +28,5 @@ "keywords": [ | ||
"bugs": { | ||
"url": "https://github.com/wizcorp/safe-timers/issues" | ||
"url": "https://github.com/Wizcorp/safe-timers/issues" | ||
}, | ||
"homepage": "https://github.com/wizcorp/safe-timers#readme", | ||
"homepage": "https://github.com/Wizcorp/safe-timers#readme", | ||
"devDependencies": { | ||
@@ -33,0 +33,0 @@ "tap-spec": "^4.1.1", |
@@ -6,7 +6,7 @@ # Safe Timers | ||
Q: What's this all about? Aren't JavaScript timers safe? | ||
A: Long story short: they're a bit broken. This module unbreaks it. | ||
A: Long story short: they're a bit broken. This module unbreaks them. | ||
Whether it's by spec, or by accident, **all** major browsers and Node.js all limit the interval a setTimeout can accept | ||
to a 32 bit signed integer. What that means in essence is that a timeout can never last longer than 24.85 days. Long | ||
enough, right? | ||
Whether it's by spec, or by accident, **all** major browsers and Node.js limit the interval a setTimeout can accept to a | ||
32 bit signed integer. What that means in essence is that a timeout can never last longer than 24.85 days. Long enough, | ||
right? | ||
@@ -13,0 +13,0 @@ The problem is that: |
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
9308