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

glob-env

v1.0.6

Published

Run command for each match of glob pattern(s) with varying env variables

Downloads

7

Readme

glob-env

Run multiple commands with variables determined by glob patterns.

Install

$ npm install -g glob-env

Usage

Running multiple instances of a script, for all combinations of "arch" and "lang" dirs:

$ glob-env arch="resources/arch/*" lang="resources/lang/*" -- npm run build-resources --lang $lang --arch $arch

Will run "npm run build-resources" for every combination. If, for example, the structure of "resources" is as follows:

  • resources/
  • resources/arch/*
  • resources/arch/x86
  • resources/arch/ia64
  • resources/lang
  • resources/lang/en_US
  • resources/lang/fr_FR

then the script will be run 4 times:

  • arch=arch/x86 lang=resources/lang/en_US
  • arch=arch/x86 lang=resources/lang/fr_FR
  • arch=arch/ia64 lang=resources/lang/en_US
  • arch=arch/ia64 lang=resources/lang/fr_FR

Using in pakcage.json

{
  "dependencies": {
    "glob-env": "^1.0.0",
    "browserify": "^13.0.1"
  },
  "scripts": {
    "build": "./node_modules/.bin/glob-env src=src/* ./node-modules/.bin/browserify src/${src} dist/${src}"
  }
}

Arguments

  • --parallel-run: commands will be executed concurrently
  • --sequential-run: commands will be executed one after the other (will take longer to complete, but require less resources)
  • --dont-collate-output: by default, command output is buffered to memory and displayed sequentially even if commands are executed in parallel. You should use this flag if process output is large
  • --dont-replace: don't replace $ variables in command line (env variables will still be set)
  • --: end of command-line flags. If present, following arguments will be passed to the executed command as-is.

Acknowledgements

This utlity was greatly inspired by glob-run which is really awesome.

License

MIT © Oded Noam