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

semantic-template

v1.1.9

Published

Template with semantic-release CI setup

Downloads

2

Readme

semantic-template

Purpose

  • Automate semantic versioning of a package, via semantic-release.
    • This bumps the semantic version of the package in package.json, as well as applying a git tag to each release.
  • Automate publishing of releases to the npm registry.

Each commit merged or pushed to master will trigger a new release.

The current semantic version of the package will be determined via its commit messages, using the conventional commits specification.

The latest version of the package will then be published to the npm registry.

The above is automated via GitHub Actions.

Use

1. Clone template:

git clone https://github.com/rom-dos/semantic-template [optional new repo name]

2. Adjust package "name" property in package.json (and other relevant fields, such as "repository", etc).

3. Add new repo on GitHub.

4. Add personal NPM_TOKEN as a repository secret:

See Adding secrets for a repository and Creating and viewing access tokens.

5. git commit && git push code to GitHub, using conventional commits.