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

prolibu-cli

v1.0.1

Published

Prolibu command line interface

Downloads

15

Readme

prolibu-cli

Prolibu command line interface

Creating an executable NPM package and using it

This short guide explains how to create an NPM package that can be called as a script from another project. For clarity: The package to execute will be called: Module The place where you use it: Application

1. Build your module

Create a standard module ignore command line parsing Your entry point index.html should be callable using require()

Paths

If your module is split in multiple files make sure to use full paths to include them. For example:

/* Files at lib:
- a.js
- b.js

In a.js:
*/
const b = require('b'); // Won't work
const b = require('./b'); // Works

1.1 Create a command line entry point

Create another entry point, a node file. Add in here: for example: cli.js

  • First line must be: #!/usr/bin/env node
  • Command line parsing
  • Help
  • Validation
  • Require your index.js (or main entry point) and run it

1.2 Modify your package.json

We'll add a line so npm knows it has to copy the cli.js into .bin

"bin": {
  "prolibu": "./cli.js"
 }
 //or 
 "bin": "./cli.js"

1.3 Publish

Check a guide on publishing to npm, when you're ready:

npm publish

Now your package is readily available to be used anywhere.

2. Use your module as script in another application

Say you build a parser, a file processor or any other cool thing. Now you want a new node application to use it when building.

2.1 Install as any other NPM module

npm install prolibu-cli --save-dev

2.2 Using it as a script

Open your package.json

  "scripts": {
    "name_to_call": "your_module_name param1 param2 param3"
  },

2.3 Run it

npm run name_to_call 

And that's it! Enjoy

References

  • https://docs.npmjs.com/files/package.json