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-run

v0.0.3

Published

Task-based bindings for running Elm in the console.

Readme

elm run

NOTE: not upgraded for 0.18 - I've since concluded that ports are a better way to do this in Elm. elm-test is a great example of a node-based Elm app that uses ports to guarantee safety.

Task-based bindings for running Elm in the console.

Inspired by elm-console

Inspired by IO

Inspired by IOSpec

Usage

Here's an interactive "Hello, World!" example:

import Run
import Stream.Writable as Run
import Stream.Readable as Run
import Task



type Model = Model

type Msg
    = Name String
    | Abort



(>>=) = Task.andThen


read : Cmd Msg
read =
    Run.stdin >>= Run.getLine
        |> Task.perform (always Abort) Name


write : String -> Cmd Msg
write name =
    Run.stdout >>= Run.putStrLn ("Hello, " ++ name ++ "!")
        |> Task.perform (always Abort) (always Abort)



init : ( Model, Cmd Msg )
init =
    ( Model, read )


update : Msg -> Model -> ( Model, Cmd Msg )
update msg _ =
    case msg of
        Name name ->
            ( Model, write name )

        Abort ->
            ( Model, Cmd.none )



main : Program Never
main =
    Run.program { init = init , update = update }

elm run operates on compiled elm files, which means the workflow looks something like this:

$ elm make --output main.js Main.elm
$ elm run main.js
World
Hello, World!

You can get the elm run command via NPM:

npm install -g elm-run

Your program ends once it is no longer waiting for Tasks to complete.

Tests

docker build -t elm-run .
docker run elm-run ./test/run-all.sh