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

@nevware21/publish-npm

v0.1.4

Published

Tools to automate the publishing packages to npm.

Downloads

464

Readme

GitHub Workflow Status (main) npm version downloads downloads

Description

Simple tools for automating the publishing of packages to npm.

Quick Start

Install the npm packare: npm install @nevware21/publish-npm --save-dev

It is suggested / recommended that you use the following definition in your package.json so that you are compatible with any future releases as they become available we do not intend to make ANY known breaking changes moving forward until v2.x

"@nevware21/publish-npm": ">= 0.1.4 < 2.x"

Create a configuration file with your group settings, where the

  • default identifies the default group when no group is passed on the command line
  • each group identifies the path to the repo where the package.json will be loaded to obtain the name
// ------------------------------
// NPM Publish group definitions
// ------------------------------
{
    "repoRoot": "../../..",
    "default": "all",
    "groups": {
        "all": [
            "./lib/pre-proc",
            "./lib/coverage-tools",
            "./lib/publish-npm"
        ],
        "preProc": [
            "./lib/pre-proc"
        ],
        "mergeCoverage": [
            "./lib/coverage-tools"
        ],
        "npmPublish": [
            "./lib/publish-npm"
        ]
    }
}

And then just used the helper in your package.json

{
    "scripts": {
        "publish-npm": "publish-npm groupName"
    }
}