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

hello-world-dev-starter

v1.1.0

Published

print hello world from console

Downloads

5

Readme

How to release npm package

npm init -y

This initializes a package.json file. Next, create an executable script file, let's say hello.js, with the following content:

#!/usr/bin/env node

console.log('Hello World!');

Now, update your package.json file to include the "bin" field:

{
  "name": "your-tool",
  "version": "1.0.0",
  "description": "Your description",
  "bin": {
    "hello": "./hello.js"
  },
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "keywords": [],
  "author": "Your Name",
  "license": "MIT"
}

Replace "your-tool" with your desired package name and update other fields accordingly. Now, you can test your tool locally by running:

npx ./

Finally, to publish your tool, you need to create an account on npm (if you haven't already). Once that's done, you can use the following command to publish your tool:

npm login
npm publish --access public

Replace "public" with "restricted" if you want to publish it as a restricted package. Now, users can install and use your tool globally with:

npx your-tool

Make sure to replace "your-tool" with the actual name of your npm package.