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

default-interface

v1.0.4

Published

Typescript interfaces with default values. Document default parameters in your `.d.ts` declaration file.

Downloads

7

Readme

default-interface

Typescript interfaces with default values. Document default parameters in your .d.ts declaration file. Tell your library users what those optional args really default to!

npm i default-interface

Example usage

// printUser.ts
import DefaultInterface from 'default-interface'

const defaults = {
    topFruit: 'orange',
    isPro: false,
} as const

type User = DefaultInterface<{
    id: number
    token: string
}, typeof defaults>

export function print(user: User) {
    const { topFruit, isPro, id, token } = { ...defaults, ...user }
    const proText = isPro ? 'a pro' : 'not a pro'
    return `A user named ${id} (${token}) loves ${topFruit}s and is ${proText}`
}
/** If you need the required version of an interface then it's one line */
export function makeUser(partial: User): Required<User> {
    return { ...defaults, ...partial }
}

If you run tsc --declaration then printUser.d.ts will have:

declare const defaults: {
    readonly topFruit: "orange";
    readonly isPro: false;
};
declare type User = DefaultInterface<{
    id: number;
    token: string;
}, typeof defaults>;
declare function print(user: User): string;
declare function makeUser(partial: User): Required<User>;

We have documented the default arguments in our types!!

Checklist

  • ✅ booleans
  • ✅ numbers
  • ✅ strings
  • ✅ array literals and arrays
  • ✅ object literals and records

Unfortunately that's all that typescript lets you put in declaration files. So defaults that are BigInts or class instances won't show up, but you rarely use those as parameters anyway.

What if I use default destructured args the normal way?

Try making a file like this and running tsc -d:

function sayMany({ times = 10, word }: { times?: number; word: string }) {
    console.log(word.repeat(times))
}

You'll get a declaration like this, and it will be very difficult for the users of your package to determine what happens when they don't specify times:

declare function sayMany({ times, word }: {
    times?: number;
    word: string;
}): void;
npm i default-interface