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-dev-env

v1.1.3

Published

Development environment for writing Elm apps

Downloads

24

Readme

elm-dev-env

Build Status npm version

Opinionated Elm development environment.

Quickstart

npm install elm-dev-env -g
elm-dev init my-app
cd my-app
elm-dev install
elm-dev start

Create a production build with elm-app build

Documentation

Installation

Node >=4 is required only as a build dependency.

npm install elm-dev-env -g

Cli

Installing elm-dev-env adds the elm-dev command:

Usage: elm-dev [options] [command]


Commands:

  install                  Installs Elm dependencies
  spec                     Runs specs
  docs                     Generates Elm documentation
  help                     Output usage information
  new|init <dir>           Scaffolds a new Elm-UI project
  server|start [options]   Starts development server
  build [options]          Builds final files

Options:

  -h, --help       output usage information
  -V, --version    output the version number
  -e, --env [env]  environment

Creating an app

To create a new app, run:

elm-dev init my-app
cd my-app
elm-dev install

This will create a directory structure like this:

my-app
├── config                  -- Configuration files
│   └── development.json
├── public                  -- Static files
│   └── index.html
├── source                  -- Elm source files
│   ├── Counter.elm
│   └── Main.elm
├── spec                    -- Specs for elm-spec
│   └── MainSpec.elm
├── stylesheets             -- Sass stylesheets
│   └── main.scss
├── .gitignore
└── elm-package.json

Also it will install Elm package dependencies with elm-github-install.

Development server

The development server can be started with elm-dev start or elm-dev server:

$ elm-dev start

Listening on localhost:8001
[BS] Proxying: http://localhost:8001
[BS] Access URLs:
 --------------------------------------
       Local: http://localhost:8002
    External: http://192.168.2.105:8002
 --------------------------------------
          UI: http://localhost:8003
 UI External: http://192.168.2.105:8003
 --------------------------------------

This will start three servers:

  • http://localhost:8001 - The application server
  • http://localhost:8002 - Proxied application server that has live reloading
  • http://localhost:8003 - Settings for the live reload server

Running specs

Specs can be run with the elm-dev spec command, which is uses elm-spec to test the components and your app.

Building production files

The final minified files can be generated with elm-ui build, this will:

  • compile and minify one main file (Main.elm by default) to dist/Main.js
  • autoprefix, compile and minify the main stylesheet file to dist/main.css
  • copy all static files from public to dist

Generating documentation

Elm documentation can be generated with the elm-dev docs command, the documentation file will be documentation.json.

What is included?

The following libraries are used: