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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@vipengele/ts

v0.2.1

Published

The batteries-included umbrella package of the vipengele TypeScript framework.

Readme

@vipengele/ts

The batteries-included umbrella package of the vipengele TypeScript framework. It re-exports the public surface of the @vipengele/ts-core-* packages from one entry point, so an application depends on a single package. It re-exports:

  • Numeric, Locale (with HourCycle, IsoWeekday, NameStyle) and the date-time values LocalDate, LocalTime, LocalDateTime, Instant, ZoneId and ZonedDateTime (with DateTimeParseError, InvalidDateTimeError, UnknownZoneError, ZoneResolutionError, isDateTimeParseError, isInvalidDateTimeError, isUnknownZoneError, isZoneResolutionError and the DateSegment, DateSegmentType, DateTimeSegment, DateTimeSegmentType, TimeSegment, TimeSegmentType, DateTimeTryParseResult, Disambiguation, IsoDayOfWeek and ZonedDateTimeOptions types);
  • Scope, normalizeAttributes (with its types) and VipengeleError;
  • from redaction, redact, secretKeys, composePolicies, redactUrl, redactQueryString and redactHeaders (with RedactionPolicy, KeyMatcher, RedactOptions, RedactStringOptions, Replacement).

Runtime detection, the logger and the error reporter are not re-exported; import them from @vipengele/ts-core-common/runtime and @vipengele/ts-core-observability.

pnpm add @vipengele/ts

Runs in the browser and in Node 24+. ESM only, side-effect free.

Numeric

Locale-aware parse, tryParse and format for numbers. Each takes a Locale and falls back to Locale.default() when it is omitted.

import { Locale, Numeric } from "@vipengele/ts";

const de = new Locale("de-DE");

Numeric.format(1234.5, de); // "1.234,5"
Numeric.parse("1.234,5", de); // 1234.5
Numeric.tryParse("abc", de); // { success: false }

Locale

A BCP 47 language tag and the calendar and clock conventions it carries. Locale.default() is the runtime's own locale. Month names run January..December and weekday names Monday..Sunday, whatever the locale's own first day of the week; firstDayOfWeek is ISO-numbered, 1 (Monday) through 7 (Sunday).

import { Locale } from "@vipengele/ts";

const locale = new Locale("en-us");

locale.tag; // "en-US"
locale.uses24Hour; // false
locale.hourCycle; // "h12"
locale.firstDayOfWeek; // 7
locale.monthNames("long")[0]; // "January"
locale.weekdayNames("short")[0]; // "Mon"
Locale.default(); // the runtime's locale

Dates and times

LocalDate, LocalTime and LocalDateTime are validated, immutable, zoneless civil values with ISO 8601 parse, tryParse and toString, LocalDate and LocalDateTime arithmetic, and now(). format, parseLocalized and tryParseLocalized take a Locale and fall back to Locale.default(); LocalDate#segments returns the locale's date pattern as year, month, day and literal segments, and LocalTime#segments its time pattern as hour, minute, second, dayPeriod and literal segments; LocalDateTime#segments joins the two patterns. A time is hour and minute unless { seconds: true } is passed to format, parseLocalized, tryParseLocalized or segments on a LocalTime or a LocalDateTime; LocalTime.dayPeriods returns the locale's AM and PM labels.

import { LocalDate, LocalTime, Locale } from "@vipengele/ts";

const de = new Locale("de-DE");
const date = LocalDate.of(2024, 3, 9);

date.toString(); // "2024-03-09"
date.format(de); // "09.03.2024"
date.plusDays(30).toString(); // "2024-04-08"
LocalDate.parseLocalized("09.03.2024", de).equals(date); // true
LocalDate.tryParse("2024-02-30"); // { success: false }
date.segments(new Locale("en-US")).map((s) => s.type); // ["month", "literal", "day", "literal", "year"]

LocalTime.of(15, 30).format(new Locale("en-US")); // "03:30 PM" (the space is the locale's own)
LocalTime.of(15, 30, 15).format(de, { seconds: true }); // "15:30:15"
LocalTime.of(15, 30).segments(de).map((s) => s.type); // ["hour", "literal", "minute"]

Invalid fields throw an InvalidDateTimeError and unparseable text a DateTimeParseError; check them with isInvalidDateTimeError and isDateTimeParseError.

Instant is a point on the UTC timeline to the nanosecond, and ZoneId a named IANA time zone that reports its UTC offset at an Instant. ZoneId.of throws an UnknownZoneError for an unknown name or a UTC-offset id; check it with isUnknownZoneError.

import { Instant, ZoneId } from "@vipengele/ts";

const instant = Instant.parse("2024-07-01T00:00:00Z");

instant.toEpochMilli(); // 1719792000000
ZoneId.of("Europe/Berlin").offsetSecondsAt(instant); // 7200

ZonedDateTime is a date and time of day in a ZoneId, with the offset it reads in there. LocalDateTime#atZone, LocalDate#atStartOfDay and Instant#atZone build one. A time the zone skips (a gap) or reads twice (an overlap) is settled by the disambiguation option, one of compatible (the default), earlier, later or reject:

| Mode | Gap (a skipped time) | Overlap (a time read twice) | | ------------ | ------------------------------------------ | ---------------------------- | | compatible | moves forward by the gap's length | the earlier instant | | earlier | moves back by the gap's length | the earlier instant | | later | moves forward by the gap's length | the later instant | | reject | throws a ZoneResolutionError | throws a ZoneResolutionError |

reject throws a ZoneResolutionError; check it with isZoneResolutionError. atStartOfDay passes the disambiguation straight through, so earlier moves a skipped midnight back into the previous date.

import { LocalDateTime, ZonedDateTime, ZoneId } from "@vipengele/ts";

const berlin = ZoneId.of("Europe/Berlin");
const skipped = LocalDateTime.parse("2026-03-29T02:30");

skipped.atZone(berlin).toString(); // "2026-03-29T03:30+02:00[Europe/Berlin]"
skipped.atZone(berlin, { disambiguation: "earlier" }).toString(); // "2026-03-29T01:30+01:00[Europe/Berlin]"

plusDays, minusDays, plusMonths and minusMonths move the local date and re-read it in the zone, so a day across a spring-forward is 23 hours; plusHours, plusMinutes, plusSeconds, plusNanos and their minus forms move the instant exactly. toString and parse use the strict ISO form 2026-10-01T14:30+02:00[Europe/Berlin]: the offset must be one the zone reads that time in, and in an overlap it picks the reading.

const meeting = ZonedDateTime.parse("2026-10-01T14:30+02:00[Europe/Berlin]");

meeting.toInstant().toString(); // "2026-10-01T12:30:00Z"
meeting.plusDays(30).toString(); // "2026-10-31T14:30+01:00[Europe/Berlin]"