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

publish-all

v1.1.2

Published

a simple cli utilitity to automatically increment version and batch-publish npm packages from multiple folders

Downloads

9

Readme

publish-all

A simple cli to publish npm packages in batch. It automatically increments last version number and then publishes each package to npm.

Release Notes

  • v1.1.0: --help and --this command arguments added

Installation

npm i -g publish-all

To see help:

publish-all --help

Usage

without config file

publish-all --folders package1,package2,folder/package3,folder2/package4

with config file

Create a new config file:

publish-all --init

This will create a .publish.conf.js file in the current folder:

module.exports = {
    folders: []
}

Add paths to packages to this file, then publish them all with:

publish-all

In both cases folders are taken relative to the folder where you run this utility, absolute paths are currently not supported, but will be supported in future.

publish just current folder

To bump version and publish just current folder:

publish-all --this