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

@levibostian/npm-module-blanky

v1.0.0

Published

replace me

Downloads

3

Readme

Latest (recommended) npm latest version Beta: npm beta version Alpha: npm alpha version

npm-module-blanky

Opinionated boilerplate used to make and deploy npm modules.

Goals of this project

  • Contain configuration files to setup all tools I tend to use in my development flow.
  • Clone, rename some files, and get developing!
  • Start with zero dependencies. I try my best to keep all npm modules as slim as possible.
  • Setup with continuous delivery to npmjs.com.
  • Publish source maps and Typescript type declarations.

Getting started

  • Enable GitHub Actions for your repository.
  • If you have not done so already, create a GitHub account for bot purposes.
  • Add your bot account in the repository /settings/access.
  • Project is setup for public publishing by default. If you would like to make your module private, edit publishConfig in package.json.
  • Create secret BOT_PUSH_TOKEN with key being a GitHub personal access token with push permission so the bot can push to the repository (the bot will be making git tags and releases on repository).

Contributors

Thanks goes to these wonderful people (emoji key)