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

@jbangdev/jbang

v0.7.1

Published

NPM for JBang - Java Script in your JavaScript

Readme

jbang-npm - Java Script in your JavaScript

Install and use JBang from NPM based projects.

Lets you use your own local scripts, JBang AppStore alias or any network reachable jar or Maven artifact.

Table of Contents

Installation

npm i @jbangdev/jbang --save

Prefer installing the package globally if you want to use it as a CLI wrapper of JBang:

npm i -g @jbangdev/jbang

Usage

You can find the complete documentation about arguments you can pass to the jbang executable here: https://www.jbang.dev/documentation/guide/latest/cli/jbang.html.

As a library

const jbang = require('@jbangdev/jbang');

jbang is an object exposing the following.

exec(string)

The jbang.exec() function accepts a string that will be passed as the command-line arguments to the jbang executable.

Example:

jbang.exec('app install --name karate-core com.intuit.karate:karate-core:RELEASE:all');

spawnSync(string)

Use spawnSync to run the command in the same process/stdin/signals.

await jbang.spawnSync('app install --name karate-core com.intuit.karate:karate-core:RELEASE:all');

Primarily used by the jbang-npm CLI.

As a CLI

Package preferably installed globally, you can run in a shell the command named jbang-npm. jbang-npm is a simple wrapper of the installed jbang executable which prevents you to manually add the command to your path.

Example:

jbang-npm app install --name karate-core com.intuit.karate:karate-core:RELEASE:all

You can also use npx:

npx jbang quarkus@quarkusio

Behind the scenes

This will look for jbang in path and if not available install it before executing jbang.

Using as a dependency

In most cases you should be able to use JBang directly in node scripts.

But if you want to provide more customization you can create your own "wrapper" NPM package. One of the advantages is that you can pre-install the library dependencies needed at the time of npm install (just by calling --help or a similar "no op" command) so that the user-experience when running the first command after install is better.

For an example, refer to the @karatelabs/karate NPM package.