Socket
Socket
Sign inDemoInstall

safe-timers

Package Overview
Dependencies
Maintainers
2
Versions
4
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

safe-timers - npm Package Compare versions

Comparing version 1.0.0 to 1.0.1

8

package.json
{
"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:

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc