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

david-test-module

v1.12.10

Published

The objective of this lab is to experiment some key npm features including:

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

davidhe1127davidhe1127

Keywords

Readme

david-test-module

It's a useless module with the purpose of experimenting npm packages releasing workflow.

To streamline release process, we will use semantic-release to assist with this.

Normal release workflow

Same as what is currently in place.

Prerelease workflow

  • Make sure pre-release branch is in sync with master
  • Add pre-release features on pre-release branch
  • Run semantic-release from pre-release branch which will result in x.x.x-prerelease.1
  • Keep adding them if there is more
  • Once you are happy with it, merge into master and release from there to create a GA. Note, need to check no prerelease dep is included.

Rules

  1. Never ever manually modify npm versions or github tags and releases. Failing to do this could result in a big confusion for semantic-release to work out the version it needs to release.
  2. When determining the next release, semantic-release will look through commit history to find the last one on the current branch:
* 590e7a2 - (tag: v1.2.0) chore(release): 1.2.0 [skip ci] (19 hours ago) <semantic-release-bot>

So, in this case, semantic-release will target 1.3.0 for the next release.