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

nestjs-backend-common

v1.4.0

Published

All the utility functions and common modules I usually use in my NestJS applications will be published and maintained here.

Readme

NestJS Backend Common

All the utility functions and common modules I usually use in my NestJS applications will be published and maintained here.

[!NOTE]

Right now you might need to install @nestjs/graphql even though your developing a RESTful API. If that is the case open an issue with this title: "split package or modularize peer deps" (search for one first though), we can discuss how should we split this library into smaller libraries.

📚 View Full API Documentation.

📦 View the package on NPM.

Why nestjs-cls Is Peer Dependency?

This is because we wanna share the same storage between our App and this library. Thus we have to define it as peer dependency;

Peer Dependencies: These are dependencies that your project hooks into or modifies in the parent project, usually a plugin for some other library or tool. Peer dependencies are not automatically installed by npm. Instead, they are only checked for, ensuring that the parent project (the project that will depend on your project) has a dependency on the project you hook into. For example, if you create a plugin for a library like Chai, you would specify Chai as a peer dependency. This ensures that the user of your plugin has the correct version of Chai installed.

FAQ

  • NPM ain't installing this library:
    npm error Cannot read properties of null (reading 'matches')
    npm error A complete log of this run can be found in: /home/mjb/.npm/_logs/2026-02-21T20_28_22_477Z-debug-0.log
    tl;dr would be either remove it from package.json and try to install it. Or use pnpm (learn more).