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

@mhilx/greeting

v1.0.1

Published

This is a demo npm package

Downloads

5

Readme

MHILX NPM Package

Install Package

npm install @mhilx/greeting --registry=https://npm.pkg.github.com
npm install @mhilx/greeting --registry=https://registry.npmjs.org

Usage Example

import sayHello from "@mhilx/greeting";
console.log(sayHello("World"));

How to publish a package to GitHub Packages

Initialize NPM in your project

npm init -y

This command will create a package.json file.

Create a personal access token

To publish your npm package using a GitHub token, you need to select the appropriate scopes when creating the token. The scopes determine the permissions and access levels that the token will have. Here are the recommended scopes for publishing an npm package:

  1. repo: This scope is required to access the repository where your npm package is located. It allows the token to read and write repository-related information.

  2. write:packages: This scope is required to publish packages to the GitHub Packages registry. It allows the token to publish, update, and delete packages associated with the repository.

  3. read:packages: This scope is required to install packages from the GitHub Packages registry. It allows the token to read and download packages associated with the repository.

  4. delete:packages: This scope is optional but recommended if you want to have the ability to delete packages from the GitHub Packages registry using the token.

When creating your GitHub token, make sure to select these scopes to ensure that you have the necessary permissions to publish your npm package.

Create .npmrc file at root of project and the following lines

@NAMESPACE:registry=https://npm.pkg.github.com
//npm.pkg.github.com/:_authToken=<YOUR_TOKEN>

Publish Package

npm publish --access=public