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

npm-publish-pkg

v1.2.0

Published

NodeJs command line tool for deploying packages to NPM repository

Downloads

11

Readme

npm-publish-package

Script for publishing npm to Npm repository.

Description

This package is used as binary nodejs package. That means it can be used from command line if installed globaly. Running this package will update version according parameters. Then it will publish module to npm registry (repository). It is similar to npm version but it does not force pushing to git.

Command line usage

After global installation (with proper configuration of npm registry): npm install -g npm-publish-package you can use following to display help: npp -h. You can also use this without global installation. You can put it into devDependencies and use it in package.json scripts section.

npm-publish-package (npp)

  Application used for publishing packages into npm repository, with auto version increment.

Options

  -h, --help                                  Displays help for this command line tool.
  -r, --registry <url>                        Npm registry (repository) url address.
  -p, --pre                                   Indication that version should be set to prerelease version.
  -b, --buildNumber                           Indicates that build number of version should be incremented.
  -m, --majorNumber                           Indicates that major number of version should be incremented.
  -v, --specificVersion <version>             Specific version that is going to be set. If this is set overrides any other
                                              version parameter.
  -t, --targetTag <tag>                       Tag that will be assigned to published package. If not specified 'latest' is
                                              used for normal version and 'pre' is used for prerelease version.
  -s, --preReleaseSuffix <preReleaseSuffix>   Suffix that will be added to version number. If not specified 'pre' is used.
                                              It is not used without 'pre' parameter.
  -d, --dryRun                                Runs script as dry run. Displaying expected version and expected command for
                                              publising

Examples

  > npp                           Deploys package to npm default repository and increases minor version number. i.e. 1.1.2 => 1.2.0 with tag "latest"
  > npp -r "http://registryUrl"   Deploys package to npm "http://registryUrl" repository and increases minor version number. i.e. 1.1.2 => 1.2.0 with tag "latest"
  > npp -p                        Deploys package to npm default repository and sets version as prerelease version. i.e. 1.1.2 => 1.2.0-pre.0 with tag "pre"
  > npp -p -b                     Deploys package to npm default repository and sets version as prerelease version. i.e. 1.1.2 => 1.1.3-pre.0 with tag "pre"
  > npp -b                        Deploys package to npm default repository and increments build version number. i.e. 1.1.0 => 1.1.1 with tag "latest"
  > npp -m                        Deploys package to npm default repository and increments major version number. i.e. 1.1.0 => 2.0.0 with tag "latest"
  > npp -v "3.0.0"                Deploys package to npm default repository and sets specific version. i.e. 1.1.0 => 3.0.0 with tag "latest"
  > npp -t "stable"               Deploys package to npm default repository and increases minor version number. i.e. 1.1.2 => 1.2.0 with tag "stable"
  > npp -p -s "beta"              Deploys package to npm default repository and increases minor version number and uses "beta" version suffix. i.e. 1.1.2 => 1.2.0-beta.0 with tag "pre"

Release Log

Description of release versions

Version 1.2.0

  • Changed computation of next version. Now its using semver for this operation.
  • Added support for dry run, which will show what will be result of action without doing anything
  • Added way how to specify pre release suffix