npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

blind-date

v3.3.0

Published

A simple library to provide type-safety for immutable and `===`able dates in TypeScript using opaquely-typed strings.

Downloads

164

Readme

Blind Date

A simple library to provide type-safety for immutable and ===able dates in TypeScript using opaquely-typed strings.

Strings are the best representations for dates and times in JavaScript when you care about immutability and sameness, such as when you're working with React components. Strings are also best when you're working with JSON, such as when using an API. You can use your favourite library to work with dates and times, but use Blind Date to represent the results.

Using

npm install blind-date
import {
	toLocalDateString,
	toLocalTimeString,
	toOffsetDateTimeString,
	toLocalDateTimeString,
	LocalDateTimeString,
	LocalDateString,
	LocalTimeString,
	OffsetDateTimeString
} from 'blind-date'

with Moment.js

import moment from 'moment'

const exampleMoment: moment.Moment = moment('22/1/2021 13:57', 'DD/MM/YYYY HH:mm')

const localDate: LocalDateString = toLocalDateString(exampleMoment)
// 2021-01-22

const localDateTime: LocalDateTimeString = toLocalDateTimeString(exampleMoment)
// 2021-01-22T13:57:00

const localTime: LocalTimeString = toLocalTimeString(exampleMoment)
// 13:57:00

const offsetDateTime: OffsetDateTimeString = toOffsetDateTimeString(exampleMoment)
// 2021-01-22T13:57:00+13:00

with Luxon

import { DateTime } from 'luxon'

const exampleDateTime: DateTime = DateTime.local(2021, 1, 22, 13, 57)

const localDate: LocalDateString = toLocalDateString(exampleDateTime)
// 2021-01-22

const localDateTime: LocalDateTimeString = toLocalDateTimeString(exampleDateTime)
// 2021-01-22T13:57:00

const localTime: LocalTimeString = toLocalTimeString(exampleDateTime)
// 13:57:00

const offsetDateTime: OffsetDateTimeString = toOffsetDateTimeString(exampleDateTime)
// 2021-01-22T13:57:00+13:00

with strings

const localDate: LocalDateString = toLocalDateString('2021-01-22')

const localDateTime: LocalDateTimeString = toLocalDateTimeString('2021-01-22T13:57:00')

const localTime: LocalTimeString = toLocalTimeString('13:57:00')

const offsetDateTime: OffsetDateTimeString = toOffsetDateTimeString('2021-01-22T13:57:00-08:00')

with literal values

const localDate: LocalDateString = toLocalDateString(2021, 1, 22)
// 2021-01-22

const localDateTime: LocalDateTimeString = toLocalDateTimeString(2021, 1, 22, 13, 57, 0)
// 2021-01-22T13:57:00

const localTime: LocalTimeString = toLocalTimeString(13, 57)
// 13:57:00

const offsetDateTime: OffsetDateTimeString = toOffsetDateTimeString(2021, 1, 22, 13, 57, 0, 0, -480)
// 2021-01-22T13:57:00-08:00

Or using object literals:

const localDate: LocalDateString = toLocalDateString({ year: 2021, month: 1, day: 22 })
// 2021-01-22

const localDateTime: LocalDateTimeString = toLocalDateTimeString({
	year: 2021, month: 1, day: 22, hours: 13, minutes: 57
})
// 2021-01-22T13:57:00

const localTime: LocalTimeString = toLocalTimeString({ hours: 13, minutes: 57 })
// 13:57:00

const offsetDateTime: OffsetDateTimeString = toOffsetDateTimeString({
	year: 2021, month: 1, day: 22, hours: 13, minutes: 57, offset: -480
})
// 2021-01-22T13:57:00-08:00

with millis

const millis = 1611277020000

const localDate: LocalDateString = toLocalDateString(millis)
// 2021-01-22

const localDateTime: LocalDateTimeString = toLocalDateTimeString(millis)
// 2021-01-22T13:57:00

const localTime: LocalTimeString = toLocalTimeString(millis)
// 13:57:00

const offsetDateTime: OffsetDateTimeString = toOffsetDateTimeString(millis)
// 2021-01-22T13:57:00+13:00

Compatibility

Blind Date uses ISO8601-formatted strings, and is compatible with Moment, DateTime from Luxon, DayJs, and JavaScript Date. Blind Date itself uses Luxon internally, and will support the others only if they are used in your project as it doesn't depend on them.

The benefit of strings and the problem with Dates

Strings have two useful properties in JavaScript:

  • they are immutable
  • two strings that have the same contents are the exact same string, i.e. they === each other (refer to MDN)

Conversely JavaScript's Date suffers from being mutable. You can call setTime on it and change the value the Date object contains. Furthermore, two Dates that represent exactly the same time are not necessarily ===.

This makes strings a better representation than Date for dates and times in JavaScript. The second property of strings also makes strings a better representation than other date libraries that return their own object or function (as two identical values aren't ===).

Immutability and sameness provide benefits when using React, as you avoid broken and unnecessary re-rendering due to mutated objects and or objects that have changed (according to === and Object.is()), but aren't actually different values.

Opaque types

The problem with strings is that they look like any other string, losing the type-safety of your code. We adopt opaque types to resolve that.

Based on the article Stronger JavaScript with Opaque Types, we provide opaque types to represent our date and time values, so that you can maintain type-safety.

The types we define are:

  • LocalDateTimeString e.g. "2020-12-05T09:44:00"
  • LocalDateString e.g. "2020-12-05"
  • LocalTimeString e.g. "09:44:00"
  • OffsetDateTimeString e.g. "2020-12-05T09:44:00+12:00"

The values are still strings. The typeof still returns string, but TypeScript sees them as distinct from string so if you declare a parameter of type LocalDateTimeString you cannot simply pass a string to it, you have to first convert the string (or whatever else) to a LocalDateTimeString.

Conversion functions

We provide conversion functions in order to create the various opaque types from: ISO8601 formatted strings, a UNIX epoch timestamp in millis, a Moment, DayJs, DateTime from Luxon, JavaScript Date, and Blind Date's own object literals.

export type DateLike = string | number | moment.Moment | Dayjs | DateTime | Date | LiteralLocalDate | LiteralLocalDateTime | LiteralLocalTime | LiteralOffsetDateTime

export function toLocalDateTimeString(date: DateLike): LocalDateTimeString;
export function toLocalDateString(date: DateLike): LocalDateString;
export function toLocalTimeString(date: DateLike): LocalTimeString;
export function toOffsetDateTimeString(date: DateLike): OffsetDateTimeString;

Local dates and times

A local date and or time does not include a timezone offset. A local date is well suited for a birthday, for example, as it's considered to be the same date no matter where in the world you are. A local time is well suited for a time of day such as noon, as it's 12:00pm no matter where in the world you are.

Local dates and times are also convenient when your application doesn't need to or doesn't want to consider timezones.

The toLocal... functions consider the timezone of the input date (if present), and output a local date and or time in that timezone. So even if you are in GMT+13:00 and call toLocalTimeString('1969-12-31T17:59-08:00') it will return 17:59:00 being the local time in the timezone of the offset date time provided.

Note that many date libraries discard the timezone information when parsing date times. If you do not get the results you expect, check the actual timezone information in the input to the toLocal... functions.

Type guards

We provide type guard functions for narrowing a type to one of our date and time types:

export function isLocalDateTimeString(date: unknown): date is LocalDateTimeString;
export function isLocalDateString(date: unknown): date is LocalDateString;
export function isLocalTimeString(date: unknown): date is LocalTimeString;
export function isOffsetDateTimeString(date: unknown): date is LocalDateString;

Passing any constant or variable to one of these functions will check to see if it is a string that matches the required format, and TypeScript will then treat your constant or variable as that type.

For example:

import { isLocalDateTime } from 'blind-date'

function handleDateTime(value: string) {
	if (isLocalDateTimeString(value)) {
		// value is now typed LocalDateTimeString
	}
}

Conversion to JavaScript Date

Blind Date can convert any date format it supports, including its own string types, to a JavaScript Date:

export function toDate(date: DateLike): Date

Validity

Some date formats can represent invalid dates, such as moment, DateTime and JavaScript's Date (when the time is NaN). Blind Date can test any date format it supports to check if it's valid.

export function isValid(date: DateLike): boolean

Note that Blind Date cannot represent an invalid date as a string, so an error will be thrown if an invalid date is passed to any of the to... functions.