Generates a timestamp down to the microsecond
Timestamp for 64-bit time_t, nanosecond precision and strftime
Capture and retrieve the last time a function was run
A versatile precision timer hook for React. Doubles as a stopwatch.
Get the quickest, most high-resolution timestamp possible in node or the browser
The RAW rational numbers library
An arbitrary-precision Decimal type for JavaScript.
Convert values with PostCSS (e.g. ms -> s)
Find the decimal precision of a given number
A node.js client for graphite.
JSON.parse with bigints support
JavaScript string formatting utilities for Vega.
An mutable object-based log format designed for chaining & objectMode streams.
RFC9562 UUIDs
Perform addition, subtraction, multiplication and division operations precisely using javascript
Double-precision complex number functions.
Single-precision complex number functions.
Convert a double-precision floating-point number to the nearest single-precision floating-point number.
Type definitions for values used in the Solana RPC, and helper functions for working with them
Arbitrary precision decimal/hexadecimal converter.
unit bezier curve interpolation
Node.js library that communicates with Embedded Dart Sass using the Embedded Sass protocol
A JS library for finding optimal label position inside a polygon
Library to help you create a Snowflake Id or parse the same.
True/False fields have a great simplicity about them, and many times they're perfect for the job! But, it's not uncommon end up in a place where you'd really love to keep some degree of simplicity with a little more detail about when the value was changed. Sometimes you'll want to display that information to the user and other times you'll keep it for auditing or debugging purposes. Either way, boolean_timestamp makes the job easy from the beginning and adds very little code to your app.
Adds a 'friendly_timestamp' method with which you can define a pair of linkedtimestamp fields (one a raw float for precision, the other a human-readable string). See README for details.
Enjoy microsecond precision in your MySQL updated_at timestamp
ace-b36ts encodes UTC timestamps into 2-8 character Base36 IDs that sort chronologically as plain strings. Seven formats from month to millisecond precision, with split output for hierarchical directory paths.
== Time.timestamp Defines <tt>Time::timestamp</tt> and <tt>Time::unix_timestamp</tt>. See the original discussion at {Ruby-Lang}[https://bugs.ruby-lang.org/issues/8096] :call-seq: Time::timestamp -> Integer Returns a nanosecond-precision timestamp from the system's monotonic clock. Note that the resolution of the measured time is system- dependent (i.e. while the value displayed is always an integer number of nanoseconds, the values may not necessarily change in increments of exactly one). This time value does not correlate to any absolute, real-world time system; it is only useful for measuring relative (or elapsed) times at a high granularity. For example, benchmark measurements. :call-seq: Time::unix_timestamp -> Integer Time::unix_time -> Integer Returns the current real-world time as a whole number of seconds since the Epoch (1-Jan-1970). :call-seq: Time::unix_microtime -> Float Returns the current real-world time as a floating-point number of seconds since the Epoch (1-Jan-1970).
No description provided.
No description provided.
No description provided.