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 🙏

© 2026 – Pkg Stats / Ryan Hefner

elm-decode-runner

v0.3.0

Published

CLI tool to run an Elm decoder on stdin JSON

Downloads

6

Readme

elm-decode-runner

CLI tool to run an Elm decoder on JSON input from stdin.

Installation

Using npm

npm install -g elm-decode-runner

Using Nix

You can run elm-decode-runner directly from GitHub without installing:

echo '{"name":"Alice","age":30}' | nix run github:pete-murphy/node-elm-decode-runner -- Example.User.decoder

Usage

Direct Decoder Usage

echo '{"name":"Alice","age":30}' | elm-decode-runner Example.User.decoder

Discover Available Decoders

elm-decode-runner --discover

Interactive Decoder Selection (with fzf)

echo '{"name":"Alice","age":30}' | elm-decode-runner --discover

This will:

  1. Parse and validate your JSON input
  2. Discover all available decoders in your project
  3. Launch fzf to let you interactively select a decoder
  4. Run the selected decoder on your JSON input

This tool makes it easy to test Elm decoders from the command line by:

  1. Taking JSON input from stdin
  2. Running it through the specified Elm decoder
  3. Printing the result to stdout

Requirements

  • Must be run in an Elm project directory (with valid elm.json)
  • The specified decoder must be found in the module path
  • For interactive mode: fzf must be installed (optional)

Arguments

  • elm-decode-runner <Module.Path.decoderName> - Run a specific decoder
  • elm-decode-runner --discover - List all available decoders
  • echo '{}' | elm-decode-runner --discover - Interactive decoder selection

Where:

  • Module.Path is the Elm module path (e.g., Example.User)
  • decoderName is the name of the decoder function (e.g., decoder)

Examples

Success case

❯ curl -s https://jsonplaceholder.typicode.com/todos/1 | elm-decode-runner Example.Todo.decoder
{ completed = False, id = 1, title = "delectus aut autem", userId = 1 }

Discovery example

❯ elm-decode-runner --discover
Example.Todo.decoder
Example.User.userDecoder
Example.User.adminDecoder
Utils.Config.settingsDecoder

Interactive example

❯ echo '{"id":1,"name":"Alice"}' | elm-decode-runner --discover
# Opens fzf with list of decoders, after selection:
{ id = 1, name = "Alice" }

Failure case

❯ echo '{"name":"Alice","age":30}' | elm-decode-runner Example.User.decoder
Problem with the given value:

{
        "name": "Alice",
        "age": 30
    }

Expecting an OBJECT with a field named `email`

License

ISC