Comparing version 0.0.1 to 0.0.2
{ | ||
"name": "clocktick", | ||
"version": "0.0.1", | ||
"version": "0.0.2", | ||
"description": "Clock-accurate timeout for Node.js and browser", | ||
"main": "index.js", | ||
"scripts": { | ||
"build": "mkdir -p dist/ && browserify index.js --standalone clocktick -o dist/clocktick.js", | ||
"test": "node test | tap-spec" | ||
@@ -23,2 +24,3 @@ }, | ||
"devDependencies": { | ||
"browserify": "^5.10.1", | ||
"tap-spec": "^0.2.1", | ||
@@ -25,0 +27,0 @@ "tape": "^2.14.0" |
# clocktick | ||
Clock-accurate timeout for Node.js and browser. | ||
Basically it is identical to setTimeout, but it triggers callback function precisely on every second. | ||
Basically it is identical to setTimeout, but it triggers callback function precisely on the next second. | ||
## example | ||
See an example [here](http://pakastin.github.io/clocktick) | ||
## accuracy | ||
@@ -12,7 +15,2 @@ Accuracy should be around 1–2ms. | ||
## testing | ||
npm install clocktick --dev | ||
npm test clocktick | ||
## usage | ||
@@ -42,1 +40,12 @@ Usage is similar to setTimeout, but without delay parameter: | ||
clearTimeout(timeout) | ||
## testing | ||
Clone to desktop and then run following commands at clocktick folder: | ||
npm install | ||
npm test | ||
## building | ||
npm install | ||
npm run build |
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
Dynamic require
Supply chain riskDynamic require can indicate the package is performing dangerous or unsafe dynamic code execution.
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
4714
6
83
50
3
2