dmytro-y-dev / nano-date

Date class that supports up to nano seconds

Nano Date

Date class that supports up to nano seconds

All of the normal date class functions with a few additions.

If you pass a number in the constructor it will assume milliseconds however if you pass in a string of numbers it will assume nanoseconds.

const upToMillisecondPrecision  = new NanoDate(1497290225089); // assumes milliseconds
const upToMicrosecondPrecision  = new NanoDate(1497290225089.999); // assumes milliseconds
const upToNanosecondPrecision = new NanoDate('1497290225089999999'); // assumes nanoseconds

Why a string of numbers? This is because 13 digits is ~ the max you can have in javascript and not have it start rounding off and 16 digits is ~ the max you can have in a float before it too starts to round. So for our case of nanoseconds it needs up to 19 digits or more to represent time since epoch that goes far beyond what a integer or float can handle so we have to use strings. Under the hood we use a library called bignumber.js to handle the math we do on this number.

Extra available methods.

• getMicroseconds

nanoDate.getMicroseconds(); // 0 - 999

• getNanoseconds

nanoDate.getNanoseconds(); // 0 - 999

• setMicroseconds - returns the microseconds value

nanoDate.setMicroseconds(25); // 25

• setNanoseconds - returns the nanoseconds value

nanoDate.setNanoseconds(25); // 25

• toString, toUTCString & toISOStringFull - adds millisecond, microsecond, nanosecond as a decimal to the seconds

nanoDate.toString(); // ie "Mon Jun 12 2017 12:57:05.089999999 GMT-0500 (CDT)"

• valueOf && NanoDate.now() - returns a integer of millisecond precision

• valueOfWithMicro - returns a float with microsecond precision

nanoDate.valueOfWithMicro(); // 1497290225089.999

• valueOfWithNano - returns a float in a string with nanosecond precision

nanoDate.valueOfWithNano(); // "1497290225089.999999"

• getTime - returns a string in nanoseconds

nanoDate.getTime(); // "1497290225089999999"