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

@nyce/eslint-config

v1.1.0

Published

Common configuration files used across projects.

Readme

1. Install packages

This template uses PNPM instead of NPM. Compatibility with regular NPM is not guaranteed and may require some tweaking.

pnpm install

2. Set first version (0.0.0 -> 1.0.0)

git commit -m "Initial commit"
pnpm version major

3. Publish the first version of your package

pnpm publish

Testing changes locally

Run the pack command:

pnpm pack

This generates an tarball file (.tgz), installable in any (p)npm project

pnpm add ./nyce-software-ts-core-[VERSION].tgz

Publishing future versions

Important notice: A version number change and a push of commits is automatically triggered by the mentioned (p)npm commands. Please do not perform these actions manually.

Commit

Commit your changes, NOTE: do not mention/commit version numbers manually

git commit -m "DESCRIBE_YOUR_CHANGES_HERE"

Version

Run the version command, specify the type of the change (semantic versioning):

pnpm version [patch|minor|major]

Publish

Run the publish command:

pnpm publish