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 🙏

© 2024 – Pkg Stats / Ryan Hefner

nnr

v1.3.8

Published

Node based Npm Run. CLI tool to run node scripts.

Downloads

63

Readme

nnr

Node based Npm Run

Easy replacement for npm run. Just run nnr script:name instead of ~~npm run script:name~~

Install

Motivation

  • cross platform (windows and linux) script in npm-script
  • resolves
    • environment variable, possible to use only $ENV_VAR, no longer need on %ENV_VAR% on window
    • possible to use same command on windows and linux with Cygwin

Features

  • possible to run script from located .json or .yml
  • default nnr.yml detection in the current folder
  • in .yml file possible to use import array with relative and absolute path
  • in .yml file possible to use eval: for evaluate a javascript command
  • like finder search in the scripts (if string includes)
  • prompt base submenu system, please read nnr.yml#1
  • inherit npm variables
  • it provides extra NNR_ORIGINALPATH environment variable to know the original call path
  • possible to debug sequential run with -a option or NNR_ASKTOCONTINUE=true environment variable. Any key to continue or CTRL+C to terminate all process
  • possible to create custom environment variable with -g option, or use nnrg for direct call e.g: test/test.yml. It use os.tmp/.nnrenv temporary file for this operation. If -n option is set the file history will not be cleared after restart
  • desc: description tag for all script
  • run multiple npm-scripts in parallel or sequential like npm-run-all
  • all script runs inside a bash shell
  • menu control keys:
    • select: space, enter
    • one level up: esc
    • on top level: esc equals exit
    • terminate: ctrl+c

Examples

Examples are located in test/package.json file or test/test.yml or nnr.yml.

Dependencies

  • Install Cygwin
  • IMPORTANT!! Add Cygwin path to Environment variables to top level, which replace the default windows commands like find and etc.

Alt text

Usage

| command | description| | ------------- |:-------------| | nnr | without parameters it gives a nice choices menu | | nnr --help | gives a standard help manual which is generated with yargs|

Status

  • [x] support menu for select a script
  • [x] support sequential run
  • [ ] support parallel run
  • [x] support package.json file
  • [x] support *.yml file

Alternatives