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

downson-cli

v0.5.0

Published

CLI for the downson library.

Downloads

11

Readme

Downson.js CLI

A command-line downson-to-JSON converter built around the downson.js library.

What's downson? It's the new configuration/data file format, y'all've been waiting for! :rocket: Check it out at here: downson.

Installation

npm install -g downson-cli

Usage

Using downson-cli is pretty straightforward:

$ downson-cli -o hello.json
**.hello** [](right) [world!](string)
^D
$ cat hello.json
{"hello":"world!"}

The list of supported command-line arguments is as follows:

Options:
  --version     Show version number                                                               [boolean]
  -i, --input   The input file to read from. If omitted, then stdin is used.                      [string]
  -o, --output  The output file to write to. If omitted, then stdout is used.                     [string]
  -p, --pretty  Pretty-print the result.                                                          [boolean]
  -s, --silent  Ignore interpretation errors and fatal errors.                                    [boolean]
  -t, --type    Path to a module that can register custom types. Can be specified multiple types. [string]
  --help        Show help                                                                         [boolean]

Custom Types

Custom types can be registered using modules passed using the -t (-type) parameter.

Registered modules should expose a single one-parameter function, which will be called with the downson.registerType function. A module can register an arbitrary number of custom types.

An example module is as follows:

module.exports = function (register) {
    register('number', (type, value, parameters) => {
        const radix = parameters.radix || 10;

        try {
            return {
                value: Number.parseInt(value, radix)
            };
        } catch {
            return {
                error: `Could not parse ${value} as a base-${radix} number!`
            };
        }
    });
};

Exit Codes and Ouput

If the process was successful or the --silent option was set, then

  • the exit code is set to 0,
  • the data layer of the downson document is written to either the stdout or the specified output file,
  • the list of the failures is written to stderr.

If the process was successful but the downson library hit an interpretation error (and the --silent option is unset), then

  • the exit code is set to 1,
  • the presumably corrupted data layer of the downson document is written to either the stdout or the specified output file,
  • the list of the failures is written to stderr.

If downson-cli encounters a fatal error (and the --silent option is unset), then

  • the exit code is set to 2,
  • the error is written to stderr,
  • nothing is written to stdout.