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

@unaffi/schema

v1.1.8

Published

This reflects what the API returns, and not what the DB Schema looks like in MongoDB. Can be imported into any repo and be used by both TS and JS (JSDocs) code.

Readme

UNAFFI Schema

This reflects what the API returns, not what the DB Schema looks like in MongoDB.

Can be imported into any repo and be used by both TS and JS (JSDocs) code.

Installation

npm i --save-dev @unaffi/schema

Usage

Example:

/** @type {import('@unaffi/schema').Profile} */
const profile = await getProfile();

/** @type {import('@unaffi/schema').Profile[]} */
const dependants = await getDependants();

or define it at the top of the page to use the type throughout the file:

/** @typedef {import('@unaffi/schema').Profile} Profile */

/** @type {Profile} */
const profile = await getProfile();

/** @type {Profile[]} */
const dependants = await getDependants();

or define it in a types/index.js file (where the file directory, types, is a peer directory or the peer of a parent directory of the file you will be using it).

/** @typedef {import('@unaffi/schema').Profile} Profile */

and then in the svelte file you need it:

/** @type {Profile} */
const profile = await getProfile();

/** @type {Profile[]} */
const dependants = await getDependants();

NOTE: This 3rd option only works in Svelte Projects – I believe in vite projects.

Updating the Schema

  1. Bump the version in the package.json:
{
  // …existing code…
  "version": "1.0.0" // to "1.0.1"   |   Always update 3rd number, unless it is a large update (such as an extra collection added). Never update 1st number unless we restart unaffi's schema entirely.
  // …existing code…
}
  1. Create authentication token (one-time setup):

    • Go to https://www.npmjs.com/settings/YOUR_USERNAME/tokens
    • Click "Generate New Token" → Select "Granular Access Token"
    • Give it a name (e.g., "publish-token")
    • Under Packages and scopes:
      • Permissions: Select Read and write
      • Packages: Select the @unaffi/schema package (or "All packages")
    • Important: Check the "Bypass 2FA" option
    • Click "Generate Token" and copy the token

    Create a .npmrc file in the project root with:

    //registry.npmjs.org/:_authToken=YOUR_TOKEN_HERE

    Replace YOUR_TOKEN_HERE with the token you just copied.

    Security Note: Do not commit the .npmrc file content. It is in the .gitignore file.

  2. Update Github:

git add .
git commit -m "Your commit message"
git push
  1. Update npm:
npm login
npm publish --access public