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

pkg-banner

v1.0.0

Published

Easily print ASCII art and package name and version when you run your CLI tool.

Downloads

3

Readme

pkg-banner

Easily print ASCII art and package name and version when you run your CLI tool.

Install

npm i pkg-banner

How it works?

Import it and use it in your main package file.

import pkgBanner from 'pkg-banner'

// Having `index.js`, the main package file, inside `/src`.
// We use the second param to go up one level to get the project's root folder,
// where `package.json` will most likely be placed.
pkgBanner(import.meta.url, '../')

Getting the calling node module path is really hard if not impossible in node :(

This is why we have this two params being passed to pkgBanner.

If you're using CommonJS:

const pkgBanner = require('pkg-banner')

pkgBanner.default(__filename, '../')

Get app dir

pkgBanner([main-package-file], [[subdir]])

If your package is of type module (ESM) you can get the main file with import.meta.url.

The second argument specifies a sub directory, which is useful if your main file lives inside [root]/src for example, in which case you need to go up one level to get the app dir or root dir.

If you're using CommonJS you can get the main file with __filename.

Motivation

Automate the process of reading and printing the project's ASCII art, package name and version.

It's not a crazy amount of effort, but why not just import a package to solve it once and for all?

I didn't find an existing package that does exactly what I needed, so here's pkg-banner.

ASCII art

If there's a file called ascii-art.txt at your project's root pkg-banner will read it and print it.

To keep it simple, there's no option to customize this.