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

@vanillas/args

v1.0.0

Published

Parse command-line args into an object

Downloads

7

Readme

Args

Parse command-line args into an object

Installation

npm install @vanillas/args

Usage

Use it to parse Node's process.argv command-line arguments. The args are placed onto an object and if necessary for any args they are coerced to an array of values.

#/usr/bin/env node
const { spawnSync } = require("child_process")

const logger = require("@vanillas/console-logger")
const parseArgs = require("@vanillas/args")

/**
 * An example shell script written for NodeJs.
 * Demonstrates parsing of command-line args, logging, spawning additional commands, etc.
 */
function run() {
  try {
    const options = parseArgs(process.argv.slice(2))

    if (options.help || options.h) {
      console.log(`
      A CLI tool which does many cool things.

      Options:
        --cwd         The current working directory
        --log-level   Logging threshold level
        --out-dir     The output directory

      Usage:
      $ my-cli-tool build --cwd=../ --out-dir ./build
      $ my-cli-tool start --log-level=debug --cwd=$HOME
      $ my-cli-tool reset
      `)
      process.exit(0)
    }

    const { _: command } = options

    logger.setLevel = /^(trace|debug|info|warn|error|fatal)$/i.test(options.logLevel)
      ? options.logLevel.toLowerCase()
      : "info"

    logger.debug(options)

    const cwd = options.cwd || process.cwd()

    if (!fs.existsSync(cwd)) {
      throw new Error(`The directory does not exist at '${cwd}'`)
    }
    if (!fs.statSync(cwd).isDirectory()) {
      throw new Error(`The cwd should be a directory and not a file '${cwd}'`)
    }

    const spawnOptions = { cwd, stdio: "inherit" }

    logger.info(`Running the '${command}' command`)

    const startedAt = Date.now()

    let result = { status: 0 }

    if (command === "build") {
      const args = ["run", "build"]

      if (options.outDir) {
        args.push("--")
        args.push("--outDir")
        args.push(options.outDir)
      }

      result = spawnSync("npm", args, spawnOptions)
    } else {
      result = spawnSync("npm", ["run", command], spawnOptions)
    }

    if (result.status > 0) {
      logger.error(`Failed to run the '${command}' command`)
      process.exit(result.status)
    }

    const elapsedSeconds = ((Date.now() - startedAt) / 1000).toFixed("2")

    logger.debug(`Finished executing the '${command}' in ${elapsedSeconds} seconds⏱`)

    process.exit(0)
  } catch (err) {
    logger.error(err)
    process.exit(1)
  }
}

run()