nrs - npm Run Scripts

A fast, interactive TUI for running npm scripts.

Note: This project was created using Claude Code and AI tools. I am not a Rust expert, and most of the code was generated by AI. Bugs, errors, and unexpected behavior are likely. Contributions, bug reports, and PRs are welcome! If you are sensitive to AI-generated code, please use with caution.

Features

• Fast - Sub-50ms startup time (native Rust binary)
• Interactive - Beautiful TUI with fuzzy search and keyboard navigation
• Smart - Auto-detects your package manager (npm, yarn, pnpm, bun)
• Powerful - Multi-select, history tracking, script descriptions
• Zero-config - Works out of the box, optional config for power users

Quick Start

# Run in any Node.js project
cd your-project
nrs

Use arrow keys to navigate, Enter to run, or press 1-9 for quick selection.

Installation

Homebrew (macOS & Linux) - Recommended

brew install tx2z/tap/npm-run-scripts

Cargo (Windows & all platforms)

cargo install npm-run-scripts

From Source

cargo install --git https://github.com/tx2z/nrs

Shell Completions

Generate shell completions for your shell:

# Bash
nrs --completions bash > ~/.local/share/bash-completion/completions/nrs

# Zsh
nrs --completions zsh > ~/.zfunc/_nrs

# Fish
nrs --completions fish > ~/.config/fish/completions/nrs.fish

Usage

Basic Commands

# Launch interactive TUI
nrs

# Launch TUI for specific project
nrs ./my-project

# List scripts without TUI
nrs --list

# Run a specific script directly
nrs -n dev

# Rerun last executed script
nrs --last

# Run script with arguments
nrs -n test --args "--watch --coverage"

# Dry run (show command without executing)
nrs -n build --dry-run

Options

nrs [OPTIONS] [PATH]

ARGUMENTS:
  [PATH]    Path to project directory (default: current directory)

OPTIONS:
  -h, --help              Show help message
  -V, --version           Show version
  -L, --last              Rerun last executed script
  -l, --list              List scripts non-interactively
  -n, --script <NAME>     Run script directly without TUI
  -a, --args <ARGS>       Arguments to pass to the script
  -e, --exclude <PATTERN> Exclude scripts matching pattern (repeatable)
  -s, --sort <MODE>       Sort mode: recent, alpha, category
  -r, --runner <RUNNER>   Override package manager: npm, yarn, pnpm, bun
  -d, --dry-run           Show command without executing
  -c, --config <PATH>     Path to config file
      --no-config         Ignore config files
      --debug             Enable debug output
      --completions <SHELL>  Generate shell completions

Keyboard Shortcuts

Navigation

Actions

Filtering & Sorting

General

Configuration

nrs works without configuration, but you can customize it with a config file.

Config File Locations

1. .nrsrc.toml in project directory
2. ~/.config/nrs/config.toml (global)

Example Configuration

# ~/.config/nrs/config.toml

[general]
# Default package manager (overrides auto-detection)
runner = "pnpm"

# Default sort mode: "recent", "alpha", "category"
default_sort = "recent"

# Show command preview in description panel
show_command_preview = true

[appearance]
# Show icons
icons = true

# Show help footer
show_footer = true

# Compact mode (less padding)
compact = false

[filter]
# Search in descriptions too
search_descriptions = true

# Enable fuzzy matching
fuzzy = true

[history]
# Enable history tracking
enabled = true

# Max projects to remember
max_projects = 100

# Max scripts per project
max_scripts = 50

[exclude]
# Global patterns to exclude
patterns = [
  "pre*",
  "post*",
]

[scripts]
# Custom descriptions (override package.json)
[scripts.descriptions]
dev = "Start development server"
build = "Build for production"

# Script aliases
[scripts.aliases]
d = "dev"
b = "build"
t = "test"

Project-Level Config

Create .nrsrc.toml in your project root:

[general]
runner = "yarn"

[exclude]
patterns = ["internal:*"]

Package Manager Detection

nrs automatically detects your package manager:

1. --runner CLI flag (highest priority)
2. runner in config file
3. packageManager field in package.json
4. Lock file detection:
   • bun.lockb → bun
   • pnpm-lock.yaml → pnpm
   • yarn.lock → yarn
   • package-lock.json → npm
5. Fallback: npm

Script Descriptions

nrs reads script descriptions from multiple sources:

scripts-info (recommended)

{
  "scripts": {
    "dev": "vite",
    "build": "vite build"
  },
  "scripts-info": {
    "dev": "Start development server",
    "build": "Build for production"
  }
}

ntl.descriptions

{
  "scripts": { "dev": "vite" },
  "ntl": {
    "descriptions": {
      "dev": "Start development server"
    }
  }
}

Comment format

{
  "scripts": {
    "//dev": "Start development server",
    "dev": "vite"
  }
}

Comparison with ntl

Exit Codes

Contributing

Contributions are welcome! Please see CONTRIBUTING.md for guidelines.

Development

# Clone the repository
git clone https://github.com/tx2z/nrs
cd nrs

# Run tests
cargo test

# Run with debug output
cargo run -- --debug

# Build release
cargo build --release

License

MIT License - see LICENSE for details.

Acknowledgments

• ratatui - TUI framework
• ntl - Inspiration for this project
• clap - CLI argument parsing