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 🙏

© 2026 – Pkg Stats / Ryan Hefner

template-npmjs

v0.0.13

Published

Template to create a new npmjs lib

Readme

template-npmjs

Template to create a new npmjs lib with typescript, tests and ci

image image image image image image

Technologies:

Examples

Installation

npm install template-npmjs

Usage

// javascript
const templateNpmjs = require('template-npmjs')
// typescript
import templateNpmjs from 'template-npmjs'
// Calling example function
templateNpmjs.greeter('Johnn Doe')  // Hello John Doe!

Prerequisites

Quick start

# Clone repository
$ git clone [email protected]:leal32b/template-npmjs.git <YOUR_PROJECT_NAME>
# Go into the repository
$ cd <YOUR_PROJECT_NAME>
# Run setup
$ npm run setup

Npmjs config

  • Click on your profile picture and then "Access Tokens"
  • Click on "Generate New Token"
  • Provide your password if asked
  • If the generated token is of type Read-only, delete this token and click on "Generate New Token" again
  • Select type Automation and click on "Generate Token"
  • Copy/save this value (it won't be showed ever again)

Circleci config

  • Allow uncertified orbs (needed for codecov orb):
    • Go to "Organization Settings" / "Security" and set "Allow Uncertified Orbs" to Yes
  • Project set up:
    • Go to "Projects", find this repository and click on "Set Up Project"
    • Choose "Fatest" option (Use the .circleci/config.yml in my repo)
    • Insert "main" in the branch input field
    • Click on "Set Up Project"
    • First workflow run will fail on "release" step
    • Go to "Project Settings" / "Environment Variables" and click on "Add Environment Variable" to add a "Name" and a "Value" for each one of this: | Name | Value | |--------------------|---------------------| | EMAIL | <your_email> | | GIT_AUTHOR_NAME | <github_username> | | GIT_COMMITTER_NAME | <github_username> | | NPM_TOKEN | <previously_copied/saved_npmjs_access_token> |
    • Go to "Project Settings" / "SSH Keys" add a "User Key" (needed to push to github)
    • Go back to project's main page and click on "Rerun workflow from start" ("Actions" column)

Github config [optional]

  • Go to repository "Settings" / "Branches"
  • Click on "Add rule"
  • On Branch name pattern, insert main
  • Check this options:
    • Require a pull request before merging
      • Require approvals
      • Dismiss stale pull request approvals when new commits are pushed
      • Require review from Code Owners
    • Require status checks to pass before merging
      • Require branches to be up to date before merging
        • Search and add this Status checks: ci/circleci: build, ci/circleci: test
  • Click on "Create"

Badges [optional]

  • Adjust shields.io urls in this README

Licence

MIT