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

super-nasty-buildkite-agent

v0.2.0

Published

Because Rob told me so

Downloads

63

Readme

Simple npm Package

A simple npm package for demonstration purposes and use in a Node.js app.

Known Vulnerabilities GitHub Discord Twitch Status Twitter Follow

Get Started

Follow these steps to publish your own npm package for your own project or using this project.

This is using the CommonJS module format for use in Node.js apps. You can read more about CommonJS vs. ESM module formats in Node.js on the LogRocket Blog

  1. Create a GitHub Repository
  2. Clone the repo locally. Example git clone https://github.com/clarkio/simple-npm-package.git
  3. Open your terminal and change directories to the folder of your cloned project. Example cd simple-npm-package
  4. Run npm init -y to create a package.json file. Note: if you cloned this repository you won't need to do this step.
  5. Update package.json name property with a scoped name. Example @clarkio/simple-npm-package. Be sure to use your username or organization name instead of mine.
  6. Write code for the package (or just use the hello world example in index.js)
  7. Sign up with npm. Also for better security be sure to enable two-factor authentication on your npm account.
  8. Sign in with your npm account in your terminal using the command npm login and follow the on-screen instructions.
  9. Run npx npm-packlist to see the contents that will be included in the published version of the package.
  10. Run npm publish --dry-run to see what would be done when actually running the command.
  11. Run npm publish --access=public to actually publish the package to npm. Note: --access=public is needed for scoped packages (@clarkio/simple-npm-package) as they're private by default. If it's not scoped and doesn't have the private field set to true in package.json it will be public as well.