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 🙏

© 2025 – Pkg Stats / Ryan Hefner

sync-package-description-cli

v1.0.2

Published

Synchronize an npm package.json description to Github.

Readme

sync-package-description-cli

Ever notice how the description in your package.json file and your Github repo description don't quite match?

This module will help you fix that.

install

Install it as a CLI module:

npm install -g sync-package-description-cli

configure

You will need one of these auth objects and you will need it available as a JSON-stringified object in the environment variable SYNC_PACKAGE_DESCRIPTION_AUTH.

Go create a token and give it Full control of private repositories. (If you know a more restrictive permission that still works, please file an issue and let me know!)

It's probably going to be easiest to add it to your ~/.profile file:

export SYNC_PACKAGE_DESCRIPTION_AUTH='{"type":"token","token":"<TOKEN VALUE>"}'

(Note the single quotes surrounding the JSON object.)

test

Make sure everything is configured correctly by passing it the test parameter:

sync-package-description test
# Success!

run it for a single module

Go into some module folder that you want to sync, and run the command:

sync-package-description

If the operation is a success, there will be no output (the application will exit with a 0). Check your Github repo to see your updated description!

You can run it in verbose mode:

sync-package-description -v
# Updated Github description for 'your-module-name'.

run automatically

A good way to have this run automatically might be to add it to your ~/.profile script as part of a set of operations you should be running each time you npm publish.

Here is the section of my own ~/.profile script:

export SYNC_PACKAGE_DESCRIPTION_AUTH='{"type":"token","token":"<TOKEN>"}'
# npm publishing hooks
alias pre-version='git diff --exit-code && npm prune && npm install -q && npm test'
# scroll to the end to see the command
alias post-version='(npm run build; exit 0) && git diff --exit-code && git push && git push --tags && npm publish && sync-package-description'
# use these to publish versions to npm
alias patch="pre-version && npm version patch && post-version"
alias feature="pre-version && npm version minor && post-version"
alias breaking="pre-version && npm version major && post-version"

license

Published and released under the VOL.

<3