npmpackage.info

Gathering detailed insights and metrics for fuzz-run

fuzz-run - 3.0.0 | npmpackage.info

fuzz-run

:runner: Run all your NPM scripts more easily with fuzzy matching Run all your NPM scripts more easily with fuzzy matching

3.0.0

MIT

JavaScript

13.54 kB

2.4

Installations

npm install fuzz-run

Developer Guide

BETA

Typescript

No

Module System

ESM

Min. Node Version

>=18

Node Version

18.19.0

NPM Version

10.2.5 Pull Requests

Open

0

Total

2

Closed

0

Merged

2

Issues

Open

0

Total

1

Closed

1

Releases

3.0.0

Updated on Jan 11, 2024

2.2.0

Updated on Mar 15, 2022

2.1.0

Updated on Mar 01, 2022

2.0.0

Updated on Mar 01, 2022

View All 4 releases

Languages

JavaScript

JavaScript (100%)

Developer

sinedied

Download Statistics

Total Downloads

Last Day

Last Week

Last Month

Last Year

GitHub Statistics

MIT License

3 Stars

52 Commits

2 Watchers

1 Branches

2 Contributors

Updated on Jan 23, 2025

Maintainers

View All 2 Contributors

Package Meta Information

Latest Version

3.0.0

Package Id

fuzz-run@3.0.0

Unpacked Size

13.54 kB

Size

5.27 kB

File Count

NPM Version

10.2.5

Node Version

18.19.0

Published on

Jan 11, 2024

Total Downloads

Cumulative downloads

Total Downloads

NaN

Last Day

NaN

Compared to previous day

Last Week

NaN

Compared to previous week

Last Month

NaN

Compared to previous month

Last Year

NaN

Compared to previous year

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

chalk-template cross-spawn fuzzysort

Dev Dependencies

jest semantic-release semantic-release-npm-github xo

:runner: fuzz-run

Node version

Run all your NPM scripts more easily with fuzzy matching.

demo gif

Features:

Fuzzy matching of NPM script name, optimized for commands (see alternatives)
Yarn and PNPM support: automatically detect the package manager used and adapt commands accordingly
No need for -- to pass extra options when using NPM
Extra actions for common recurrent tasks

Installation

1npm install -g fuzz-run

CLI Usage

1Usage: fr <fuzzy_script_name>|<action> [script_options]
2Actions:
3  -u, --update   Show outdated packages and run an interactive update
4  -r, --refresh  Delete node_modules and lockfile, and reinstall packages

If no arguments are provided, it will list all available scripts.

As the name of the script to run is fuzzy matched, you can try:

typing only some letters of the script name, regardless of their position (first letters weights more), like t for test script
typing first letter of compound script names like tc for test:ci script
making some typos, like ets for test script

Note that you can use the alias nr (for npm run) instead of fr (fuzz run) if you prefer :wink:

You can pass any arguments to your script if needed, like fr t --coverage. You don't need to use -- to pass extra options to your script like when using npm directly.

Actions

There are a few scripted actions you can use for common day-to-day tasks in your projects:

-u or --update: It will show outdated packages, then ask if you want to update. If you accept, it will first update all package within their allowed range according to your package.json using npm update, pnpm update or yarn upgrade. Then it will run an interactive update, using under the hood npx npm-check -u if NPM or PNPM is your package manager or yarn upgrade-interactive if you use Yarn.
-r or --refresh: It will delete node_modules folder and lockfile, and reinstall all your packages. I probably use that more than I should, but it's always a handy fix.

Package manager

Supported package managers are NPM, Yarn and PNPM.

By default, your package manager will be autodetected based on your project's lockfile format, and corresponding commands will be used.

You can also force a package manager by setting the NODE_PACKAGE_MANAGER environment variable.

API

You can also integrate this script runner in your own CLI by using the function fuzzyRun(args, packageManager):

args: array of arguments, the same you would use for the CLI usage
packageManager: optional, can be 'npm', 'yarn' or 'pnpm' to force a specific command to run the scripts. If null or undefined, it will be autodetected based on your project's lockfile format.

Example:

1const fuzzyRun = require('fuzzy-run');
2fuzzyRun(process.argv.slice(2));

Alternatives

Why making a new tool when some other exists, you might ask? Both are based on fuse.js for the fuzzy matching, which is not great for matching commands, as it doesn't weight properly specific features like subcommands separation (using characters like -, _, :) or first character of words :disappointed:

Some examples:

if you have 2 scripts test and test:ci, typing tc matches test instead of test:ci
if you have 2 scripts test:ci and other, typing t matches other

So I benchmarked many fuzzy matching libraries, and kept the best one I found suited for the job, fuzzysort, that solves these issues.

No vulnerabilities found.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

10

Dangerous-Workflow

Determines if the project's GitHub Action workflows avoid dangerous patterns.

10

License

Determines if the project has defined a license.

2

Pinned-Dependencies

Determines if the project has declared and pinned the dependencies of its build process.

0

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

0

Maintained

Determines if the project is "actively maintained".

0

Token-Permissions

Determines if the project's workflows follow the principle of least privilege.

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Security-Policy

Determines if the project has published a security policy.

0

Fuzzing

Determines if the project uses fuzzing.

0

Signed-Releases

Determines if the project cryptographically signs release artifacts.

0

Branch-Protection

Determines if the default and release branches are protected with GitHub's branch protection settings.

0

SAST

Determines if the project uses static code analysis.

0

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

Score

2.4

/10

Last Scanned on 2025-06-30

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.

Learn More