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

exec-below

v1.2.1

Published

Executes commands in nested directories

Downloads

8

Readme

exec-below

npm version npm downloads GitHub CodeQL Check This module provides a exec-below command that opens a shell in recursively in every directory below the current directory and executes the specified command.

Why?

Certain build and deployment operations require the zipping of folder content. Without this tool, individual package.json files or individually coded calls are necesary.

Global command line usage

npm install -g exec-below
exec-below "npx bestzip" "packed.zip" "*" 

NPX Usage

npx exec-below "npx bestzip" "packed.zip" "*" 

Command line usage within package.json scripts

npm install --save-dev exec-below

package.json:

{
    //...
    "scripts": {
        "build" "...",
        "zip": "exec-below '@[email protected]' '*' --depth 1",
        "upload": "....",
        "deploy": "npm run build && npm run zip && npm run upload"
    }
}

Programmatic usage from within Node.js

const execbelow = require('exec-below')

execbelow('npx bestzip', ['@PathToExecuteFrom@/../output/@[email protected]', '*'], { verbose: true, depth: 1, startPath: path.join(__dirname, './../testDir/input')).then(function() {
  console.log('all done!');
}).catch(function(err) {
  console.error(err.stack);
  process.exit(1);
});

Replacement Parameters

The following replacement parameters can be specified as part of a command or an command argument.

  • @DirectoryName@: The name of the directory. If the current directory that is processed is /home/etc/testdir1 then the replacement value is testdir1
  • @PathToDirectory@: The path to the directory. If the current directory that is processed is /home/etc/testdir1 then the replacement value is /home/etc
  • @PathToExecuteFrom@: The path to directory from which you executed the comand. If you execute the exec-below in the direcory /home/etc then the replacement value is /home/etc

Options

  • -d or --depth: Specifies the execution depth (default; 9999)
  • -s or --startPath: Starting path
  • -v or --verbose: Runs the command with verbose logging
  • --version: Shows the version of the package
  • --help: Shows help