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

up-npm

v4.3.1

Published

CLI tool written in Go to review and update your NPM dependencies, easy and fast.

Downloads

74

Readme

up-npm

CLI tool written in Go to review and update your NPM dependencies, easy and fast.

built with Codeium

Features

  • 🔍 Easily identify the update type for each package, whether it's a patch, minor, or major update.
  • 📃 Review the release notes for each package to see "what's new" before deciding whether to update.
  • 🦘 Selectively skip updates for specific packages.
  • 🛡️ Back up your package.json file before updating, ensuring you always have a fallback option if something goes wrong.

Usage

Go where your package.json is located and run:

up-npm

or

up-npm [flags]

| Flag | Description | |--------------------- |------------------------------------------------------------- | | --no-dev | Exclude dev dependencies. Default false. | | -f, --filter string | Filter dependencies by package name | | --allow-downgrade | Allows downgrading a if latest version is older than current. | | --file string | Default package.json. | | -h, --help | Display help information for up-npm. | | -v, --version | Display the version number for up-npm. |

Examples

# Update dependencies
npm-up

# Excluding dev dependencies
npm-up --no-dev

# Update only packages containing "lint"
npm-up -filter lint
npm-up -f lint

# Update some specific .json
npm-up --file my-project/package.json

Build yourself