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

containerfile

v1.4.0

Published

Containerfile parser and stringifier

Readme

containerfile

Containerfile parser and stringifier

npm install containerfile

Usage

var containerfile = require('containerfile')

var parsed = containerfile.parse(`
  FROM ubuntu:xenial
  RUN rm -f /etc/resolv.conf && echo '8.8.8.8' > /etc/resolv.conf
  RUN apt-get update
  RUN apt-get install -y git vim curl
  RUN curl -fs https://raw.githubusercontent.com/mafintosh/node-install/master/install | sh
  RUN node-install 8.9.1
`)

// prints the parsed file
console.log(parsed)

// serializes it again
console.log(containerfile.stringify(parsed))

Syntax

The format is similar to a Dockerfile.

FROM os:version
RUN shell-command
COPY from/local/file /to/container/path
ENV key=value key2=value2
ARG key=value

Alternatively if you are referencing another Containerfile or disk image you can do

FROM ./path/to/disk/image/or/containerfile

If your shell command is long you can split it into multiple lines using the familiar \\ syntax

RUN apt-get update && \\
  apt-get install -y git vim curl

To comment out a line add # infront.

To force run a command (i.e. cache bust it) you can prefix any command with FORCE.

API

var parsed = containerfile.parse(string)

Parse the content of a Containerfile. Returns an array of objects, each representing a line.

// FROM os:version
{
  type: 'from',
  image: 'os',
  version: 'version',
  path: null
}

// FROM ./path
{
  type: 'from',
  image: null,
  version: null,
  path: './path'
}

// RUN command
{
  type: 'run',
  command: 'command'
}

// COPY from to
{
  type: 'copy',
  from: 'from',
  to: 'to'
}

// ENV key=value key2="value 2" ...
{
  type: 'env',
  env: [{
    key: 'key',
    value: 'value'
  }, {
    key: 'key2',
    value: 'value 2'
  }]
}

// ARG key=value
{
  type: 'arg',
  key: 'key',
  value: 'value'
}

// ARG key
{
  type: 'arg',
  key: 'key',
  value: null
}

If a command is prefixed with FORCE, force: true will be set on the object.

var str = containerfile.stringify(parsed)

Serialize a parsed object back to the Containerfile format

License

MIT