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

@armor/npm-version-manager

v2.0.8

Published

Ensures package.json files are consistent with accepted master files.

Downloads

34

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

ssalunkessalunkeharishnethaharishnethamojo-armormojo-armorwbjarviswbjarvisarmor-prestonarmor-prestonyogeeshgcyogeeshgcrkotrarkotrasushilnpm302sushilnpm302vshivannavshivannaarmor_ciarmor_cistraineanu.armorstraineanu.armor

Keywords

Readme

npm-version-manager

Installation

npm i -g @armor/npm-version-manager

Usage

Without Args

npmvm

With Args

npmvm ./package.json --lib --site --quiet

You may optionally supply the path to the package.json file you want to analyze. Additionally, you can use these flags:

--lib

Includes the lib.master.json scripts and packages for comparison; use these if your project is a redistributable library

--site

Includes the site.master.json scripts and packages for comparison; use these if your project is a site or application. If your project is both a library and a site, you can use both in combination.

--quiet

Suppresses the output of success messages.

Ignoring Divergent Scripts

Some projects will have unique scripts or customizations to existing scripts. You can suppress error messages (downgrade from an ERROR level to a WARN level) by including a .npmvmignore file in the root of your project (or wherever you run npmvm). This file should be a newline delimited text file of all script keys you want to ignore.

Example .npmvmignore File

build
build:site:prod
postinstall

Updating

If newer versions of npmvm are available, the last output of the script will let you know. Simply run npm i -g @armor/npm-version-manager again to update to the latest version.