
Research
NPM targeted by malware campaign mimicking familiar library names
Socket uncovered npm malware campaign mimicking popular Node.js libraries and packages from other ecosystems; packages steal data and execute remote code.
safe-timers
Advanced tools
Q: What's this all about? Aren't JavaScript timers safe? 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 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?
The problem is that:
All the arguments about "you shouldn't need intervals this big anyway" go out the window the moment you provide a big one and instead of never firing, it fires immediately. This is a real problem. And so here we are, Safe Timers solves this for you.
Does that mean you should forego the browser native setTimeout and setInterval altogether? Absolutely not. Most of the time, we pass constant short intervals, in which case Safe Timers are overkill. But when your interval comes from some variable that depends on state or user input, using Safe Timers is a good idea.
Timer setTimeout(Function callback, number interval, mixed arg1, mixed arg2, ...)
Calls callback
after at least interval
milliseconds have passed. All arguments passed after the interval
will be
passed to the callback once it gets invoked. Returns a Timer
instance.
const setTimeout = require('safe-timers').setTimeout;
setTimeout(function (msg) {
console.log(msg);
}, 5000, 'Hello world');
Timer setTimeoutAt(Function callback, number timestamp, mixed arg1, mixed arg2, ...)
Calls callback
when our clock reaches the given timestamp
(in milliseconds). All arguments passed after the
interval
will be passed to the callback once it gets invoked. Returns a Timer
instance.
const setTimeoutAt = require('safe-timers').setTimeoutAt;
setTimeoutAt(function (msg) {
console.log(msg);
}, Date.now() + 5000, 'Hello world');
Interval setInterval(Function callback, number interval, mixed arg1, mixed arg2, ...)
Calls callback
after at least every interval
milliseconds. All arguments passed after the interval
will be passed
to the callback when it gets invoked. Returns an Interval
instance.
const setInterval = require('safe-timers').setInterval;
setInterval(function (msg) {
console.log(msg);
}, 5000, 'Hello world');
timer.clear() / interval.clear()
The response from safetimers.setTimeout[At]
and safetimers.setInterval
are Timer
and Interval
objects
respectively. To cancel a timer or interval, you can call clear
on it.
const setTimeout = require('safe-timers').setTimeout;
const timer = setTimeout(function (msg) {
console.log(msg); // this will never show
}, 5000, 'Hello world');
timer.clear();
FAQs
Timers with near-infinite duration support
The npm package safe-timers receives a total of 36,902 weekly downloads. As such, safe-timers popularity was classified as popular.
We found that safe-timers demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 2 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Socket uncovered npm malware campaign mimicking popular Node.js libraries and packages from other ecosystems; packages steal data and execute remote code.
Research
Socket's research uncovers three dangerous Go modules that contain obfuscated disk-wiping malware, threatening complete data loss.
Research
Socket uncovers malicious packages on PyPI using Gmail's SMTP protocol for command and control (C2) to exfiltrate data and execute commands.