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 🙏

© 2025 – Pkg Stats / Ryan Hefner

elm-stdio

v1.0.1

Published

Elm stdio server

Readme

elm-stdio npm package

elm-stdio lets you render Elm components on the server, regardless of the backend technology you're using.

As its name suggests, other processes communicate with elm-stdio using standard streams. The protocol is JSON, so any environment that can spawn a child process and write JSON to its stdin can use the server. Requests are handled serially, so responses are issued in the same order requests are received.

Installation

Using npm:

$ npm install elm-stdio min-document

Note that at this time there is a bug in min-document that handles boolean html attributes incorrectly. The patch at hassox/min-document addresses this bug. The PR requests this change be pulled upstream.

Usage

Once you've installed the server, you will have a elm-stdio binary available (assuming node_modules/.bin is in your $PATH). Execute it to start the server.

To render a React component, write a JSON blob to stdin with any of the following properties:

path            The path to a file that exports Elm with your component loaded
component       The name of the component to render (note only top level components are supported
render          The rendering method. `fullscreen` or `embed`
id              The html id attribute of the contianer DIV to render into (when using `embed`)
data            The object to pass to Elm render method

If the request is successful, the server will put a JSON blob with {"html":"..."} on stdout. If the request fails for some reason, the JSON will have an error property instead of html.

Example:

$ echo '{"path": "./server/todo.js", "component":"Todo", "render": "embed", "id": "elm-main", "data":{"getStorage":null}}' | elm-stdio

Environment

Your component file should be a self contained bundle. The file will be loaded and run.

Additionally, since react-stdio uses the stdout stream for all program output, all writes your code makes to process.stdout (including console.log statements) are redirected to process.stderr.

Embed vs Fullscreen

When rendering using the fullscreen method, the output will include the body tag.

When rendering using the embed method, the output will include the container div with the correct id attribute.

Integrations

If you'd like to add an integration here, please contact @hassox.