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

jarrod-npm-package

v1.0.2

Published

``` K:\Projects\npm\LinkedIn\npm-package>npm login Username: <username> Password: Email: (this IS public) <email address> Logged in as <username> on https://registry.npmjs.org/. ```

Downloads

5

Readme

How To Publish A Package To NPM

K:\Projects\npm\LinkedIn\npm-package>npm login
Username: <username>
Password:
Email: (this IS public) <email address>
Logged in as <username> on https://registry.npmjs.org/.
K:\Projects\npm\LinkedIn\npm-package>npm publish
npm notice
npm notice package: [email protected]
npm notice === Tarball Contents ===
npm notice 232B package.json
npm notice 95B  index.js
npm notice === Tarball Details ===
npm notice name:          jarrod-npm-package
npm notice version:       1.0.0
npm notice package size:  363 B
npm notice unpacked size: 327 B
npm notice shasum:        dd885c36ad88bd1ce2ffd9e6bf30756dfd5bf9c2
npm notice integrity:     sha512-fHCSYVM5Q/p31[...]XrZyusc/pnbOw==
npm notice total files:   2
npm notice
+ [email protected]

To Update An Existing Package

You must update the version number in package.json, and then npm publish