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

learn-npm-hello

v1.0.1

Published

Learning about NPM with a Hello

Downloads

1,350

Readme

Hello World package for NPM registry

Steps Taken

  1. Create account on NPM website or on CLI with npm adduser
  • check by hitting https://www.npmjs.org/~<username>
  1. Create new module/package
  2. npm init to setup the basic package.json information
  3. create/test the code
  4. Authorize the development machine using npm login
  5. Publish to registry with npm publish in the project directory
  6. Check http://npmjs.com/package/<package>
  7. Finally run npm install <package> to ensure the package is available for use

NPM Package Requirements

Reference NPM doc

  • package.json
  • name and version in the package.json file

Quick NPM Commands

  • npm config ls or npm get
  • show the current configuration information pulled from .npmrc
  • npm publish
  • publish the current directory's package
  • npm publish --tag beta
  • publish to NPM with the latest tag, so it will not be auto installed
  • npm version <patch|minor|major>
  • bump the package.json version information
  • if executed in GIT repository, it will auto-create a tag as well
  • npm pack
  • create a package - ZIP - of the project locally
  • local install for testing with npm install <zip file name (absolute/related) path>
  • npm install <package name>
  • npm uninstall <package name>