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

mftb-shared

v1.1.254

Published

Shared library for both back and front end.

Readme

Shared library

Shared library for both back and front end.

Types

For a methods param, if its type references an enum/interface etc defined in a package, then the associated 'types' package needs to be in 'dependencies' and not 'devDependencies'.

This is because when typescript transpiles the code it will include that package in the 'd.ts' file. When mftb-shared is later installed, the package will be referenced. If its in dependencies it will be installed, if its in devDependencies it wont be installed and you will get a typescript error in the project that consumes mftb-shared

Eg:

import jwt from "jsonwebtoken";

const signToken = (
  payload: any,
  secret: string,
  algorithm: jwt.Algorithm
): string => {
  return jwt.sign(payload, secret, { algorithm });
};

Because jwt.Algorithm is used as a param type, we need to put the types package in dependencies. ie

npm install @types/jsonwebtoken <-- correct

NOT

npm install --save-dev @types/jsonwebtoken <--- wrong