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

@gisatcz/test-package

v6.1.0

Published

Test package

Downloads

8

Readme

test-package

Auto publish configuration

$ npm install -D auto
  • create npm token at https://www.npmjs.com/settings/<username>/tokens

  • make token available as env variables (NPM_TOKEN, GH_TOKEN on ci)

  • configure ci to make auto release (full example can be seen in .github/workflows/release.yml)

$ npx auto shipit

Make first publish

Run npm publish --access public to create the package with public access

$ npm publish --access public

Mark prs for release

One of these labels have to be added to the pr in order increment right version number after it's merged into master: major, minor, patch.

Prerelease branches

This repo has dev prerelease branch.

Make sure that pr contains label specifying version number to increment

see example