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

@rhombus-toolkit/types

v1.0.1

Published

Type-level utilities: the Func family, arrays, string literals, counters and brands. No runtime.

Readme

@rhombus-toolkit/types

Type-level utilities. No runtime — every file is a .ts holding only type declarations, so the package emits no JavaScript at all while still being type-checked like ordinary source (a .d.ts would be skipped outright under skipLibCheck, which is how several of these types shipped broken).

Entry points

| Entry | Contents | | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | . | Func, AsyncFunc, Action, AsyncAction, Sub, AsyncSub, Ctor, AbstractCtor · Curry · Cast · Brand, Flavor · Identity · DeepRecord, DeepRecordItem, Dictionary, DeepDictionary, DeepDictionaryItem · Store, Inc, Dec, Add, Subtract, Multiply · UnionToIntersection · UnionToTuple, TupleToUnion · AssertNeverError · Falsy, Truthy, IsFalsy, IsTruthy, IfFalsy, IfTruthy, TypeName · Simplify, Flatten, Except, Mutable, IfEquals, WritableKeys, ReadonlyKeys, WritablePart, MakeRequired | | ./generic | The $-placeholder Func/Ctor/AbstractCtor variants | | ./array | Head, Tail, Body, Last, Length, SplitArray, Slice, Take, Skip, PartialList | | ./string | ToStringable, AsString, ToStringLiteral, Join, Split, ClearEmpties; the char alphabet (AnyChar, LetterChar, UpperCaseChar, LowerCaseChar, DigitChar, NonDigitChar, SpaceChar, NonSpaceChar, SymbolChar, WordChar, NonWordChar); the case converters (CamelCase, PascalCase, SnakeCase, KebabCase, DashCase, ConstantCase, TitleCase) |

Naming convention

Every exported type here is UpperCamel.

A lowercase type name means — and only ever means — that a runtime function of the same name is declaration-merged with it (defer, flattenMap, obj.keys). That can only happen in a package that has a runtime, so nothing in this one qualifies, and a lowercase name would be a lie about what you are importing.

The rule is applied at the definition, not at the barrel: join as Join re-exports are what it exists to prevent.

Renames

Absorbed from @rhombus-toolkit/func (whole package), @rhombus-toolkit/case-converter (whole package), and the type half of @rhombus-toolkit/type-helpers.

| Was | Is | Why | | ------------------------------------------------------- | ------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------- | | join, split, clearEmpties, asString, identity | Join, Split, ClearEmpties, AsString, Identity | the naming convention above | | toString | ToStringLiteral | says what it produces, and stops shadowing Object.prototype.toString | | isFalsy<T, TruePart, FalsePart> | IfFalsy<T, Then, Else> | it selects a branch, so it is an If; IsFalsy<T> is the new boolean-valued form (and IfTruthy/IsTruthy likewise) | | Opaque | Brand | the community term; Flavor (optional marker) ships beside it | | SnakeCase | ConstantCase | it always produced FOO_BAR; SnakeCase now produces foo_bar |

func's ./generic subpath keeps its name, so an existing @rhombus-toolkit/func/generic import moves with a one-token change.