relative-microtime
Advanced tools
Get the number of microseconds elapsed since January 1, 1970 00:00:00 UTC without fear of clock drift
This module returns the number of microseconds elapsed since January 1, 1970 00:00:00 UTC.
Note: The returned number of microseconds are locked relative to a
specific time and is therefore not subject to clock drift. This is
contrary to how Date.now() operates, whos return value (in
milliseconds) is always based on the system clock.
npm install relative-microtime --save
const timer = require('relative-microtime')()
const milli = Date.now()
const micro = timer()
console.log(milli) // 1537446194859
console.log(micro) // 1537446194859132
timer = microtime()Sync the microtime clock to the UTC wall clock.
Returns a timer function synced with the UTC time when microtime()
was called. Any clock drift that happens after the call to microtime()
will not influence the returned timer.
timer()Returns a Number representing the microseconds elapsed since the UNIX
epoch.
FAQs
Get the number of microseconds elapsed since January 1, 1970 00:00:00 UTC without fear of clock drift
We found that relative-microtime demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer 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.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.