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

tbd112922

v7.0.0

Published

Test to see the benefits of using semantic release It will follow semantic versioning with the format of v{Major}{Minor}{Patch} e.g. v1.2.3 - {Patch} → backward compatible bug fixes - {Minor} → new backward compatible features, deprecation of public api

Downloads

5

Readme

TestSemanticRelease

Test to see the benefits of using semantic release It will follow semantic versioning with the format of v{Major}{Minor}{Patch} e.g. v1.2.3

  • {Patch} → backward compatible bug fixes
  • {Minor} → new backward compatible features, deprecation of public api
  • {Major} → new backward incompatible api
  • {Major} = 0 → Initial development when anything can change
  • {Major} >= 1 → 1st public stable release

Adding a commit

Commits are added in Agular format and must be one of the following in order to create a release:

  • feat: A new feature
  • fix: A bug fix
  • docs: Documentation only changes
  • style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi -colons, etc)
  • refactor: A code change that neither fixes a bug or adds a feature
  • perf: A code change that improves performance
  • test: Add missing or correcting existing test
  • build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
  • ci: Changes to our CI Configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
  • revert: Reverts a previous commit
  • chore: Changes the build process or auxiliary tools and libraries such as documentation

Suggestions for other documentation to read