Gathering detailed insights and metrics for yoctodelay
Gathering detailed insights and metrics for yoctodelay
Gathering detailed insights and metrics for yoctodelay
Gathering detailed insights and metrics for yoctodelay
npm install yoctodelay
Typescript
Module System
Min. Node Version
Node Version
NPM Version
JavaScript (75.06%)
TypeScript (24.94%)
Total Downloads
3,744,005
Last Day
2,294
Last Week
18,142
Last Month
86,557
Last Year
768,931
MIT License
118 Stars
12 Commits
11 Forks
3 Watchers
1 Branches
5 Contributors
Updated on Jul 13, 2025
Latest Version
2.0.0
Package Id
yoctodelay@2.0.0
Size
1.99 kB
NPM Version
7.10.0
Node Version
12.22.1
Published on
Aug 14, 2021
Cumulative downloads
Total Downloads
Last Day
-11.5%
2,294
Compared to previous day
Last Week
-11.3%
18,142
Compared to previous week
Last Month
23.2%
86,557
Compared to previous month
Last Year
6%
768,931
Compared to previous year
Delay a promise a specified amount of time
It's less than half the size of the nanodelay
module.
Note: If you target Node.js 16 or later, you can use the built-in functionality instead:
1import {setTimeout as delay} from 'node:timers/promises'; 2 3await delay(100);
$ npm install yoctodelay
1import delay from 'yoctodelay'; 2 3foo(); 4 5await delay(100); 6 7// Executed 100 milliseconds later 8bar();
Delay the promise and then resolve.
Type: number
The duration to delay the promise.
It's the smallest official unit prefix in the metric system. Much smaller than nano.
Partly. The nanodelay
module was created only because the delay
module is a tiny bit larger. Well, this module is a tiny bit smaller than the nanodelay
module. Comparing size at the byte level is super silly. It doesn't matter unless the difference is more than many kilobytes. This is still a fully working module though. Go ahead and use it.
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
no dangerous workflow patterns detected
Reason
0 existing vulnerabilities detected
Reason
license file detected
Details
Reason
Found 4/12 approved changesets -- score normalized to 3
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
project is not fuzzed
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
security policy file not detected
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Score
Last Scanned on 2025-07-07
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More