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

default-value-to

v1.0.1

Published

A tiny TypeScript utility to safely provide default values for optional chaining.

Readme

default-value-to

A tiny TypeScript utility to safely transform undefined or null values into predictable defaults — designed to simplify unit testing and improve branch coverage.


Why This Package?

When mapping API data into strongly typed objects, source data often returns:

  • string | undefined
  • number | undefined

To make values safe, we usually write:

obj?.prop ?? ""

or

obj?.count ?? 0

However, in unit tests, using optional chaining (?.) creates additional branches that must be covered.

For example:

obj?.prop ?? ""

To achieve full coverage, you must mock:

  • obj undefined
  • obj defined but prop undefined
  • obj.prop defined

That increases unnecessary test complexity.


The Solution

default-value-to centralizes that nullish handling into a single utility:

defaultTo(obj?.prop, "")

Now your unit tests only need to test:

  • value defined
  • value undefined

No deep object mocking required.


Installation

npm install default-value-to

Usage

import { defaultTo } from "default-value-to";

type User = {
  name?: string;
  age?: number;
};

const user = undefined;

const name = defaultTo(user?.name, "");
const age = defaultTo(user?.age, 0);

Resulting Types

name: string
age: number

Never undefined.


API

defaultTo<T>(value: T, defaultValue: NonNullable<T>): NonNullable<T>

Returns:

  • value if not null or undefined
  • defaultValue otherwise

Example: Mapping API Data

Before:

const mapped = {
  name: apiUser?.name ?? "",
  age: apiUser?.age ?? 0
};

After:

const mapped = {
  name: defaultTo(apiUser?.name, ""),
  age: defaultTo(apiUser?.age, 0)
};

Cleaner.
More readable.
Less test boilerplate.


Designed For

  • React projects
  • TypeScript projects
  • Clean unit test coverage
  • API data transformation layers

License

MIT