https://github.com/deepsweet/nbx

▶️ Execute package binaries
https://github.com/deepsweet/nbx

bin cli npm

Last synced: about 1 year ago
JSON representation

▶️ Execute package binaries

• Host: GitHub
• URL: https://github.com/deepsweet/nbx
• Owner: deepsweet
• License: mit
• Created: 2018-06-28T20:10:09.000Z (almost 8 years ago)
• Default Branch: master
• Last Pushed: 2020-04-05T09:46:14.000Z (about 6 years ago)
• Last Synced: 2025-03-24T03:03:34.919Z (about 1 year ago)
• Topics: bin, cli, npm
• Language: Shell
• Size: 14.6 KB
• Stars: 8
• Watchers: 3
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: readme.md
  • License: license.md

Awesome Lists containing this project

README

          
# nbx

[![npm](https://img.shields.io/npm/v/nbx.svg?style=flat-square)](https://www.npmjs.com/package/nbx) [![shellcheck](https://img.shields.io/travis/deepsweet/nbx/master.svg?label=shellcheck&style=flat-square)](https://travis-ci.org/deepsweet/nbx)

Execute package binaries.

* `yarn ` is a mess because it's trying to resolve a target from 3 (three) different places: yarn internal commands, npm scripts and `./node_modules/.bin/`

* `npx ` is doing too much, like checking in `$PATH` or autoinstalling a package if it's not found

* `./node_modules/.bin/` in `$PATH` is very implicit and even wider guess than `yarn `

* shell aliases/functions are nice but not installable/shareable (?)

* `./node_modules/.bin/` every time is just too verbose

## Install

```sh

$ yarn global add nbx

# or

$ npm install --global nbx

```

## Usage

```sh

$ nbx

One of the following binary names is required:

# …

```

```sh

$ nbx webpack --help

```

## Windows?

It probably just works if you are using that native "Linux in Windows" thing, `nbx` is just an extremely primitive Bourne Shell (or whatever compatible `/bin/sh` is) script.