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

reem

v0.0.5

Published

rambunctious static site generator

Downloads

17

Readme

Reem

Reem is a static site generator written in JavaScript. Reem reads a source directory into a tree structure, which is then processed internally and then by customizable plugins and middleware. The final tree is rendered and written to the output directory, and the site is ready to host.

Reem has both a command-line interface and a programming interface suitable for personal and automated production of static sites.

Reem is realistic to people's needs; specializing to no single use case, but advocating specialization as much as possible.

Getting Started

Installation

Reem is available on npm and should be installed globally for the command-line interface.

npm -g install reem

Initialization

In a chosen static site directory run:

reem --init

Which creates the default folder/file structure:

site
|- layout/
|- output/
|- source/
|- reemfile.js

The layout directory contains the templates, includes, and other rendering files. The source directory contain posts, assets, directories, and any other files. The output directory contains, well, the output.

The reemfile.js is where Reem can be configured; changing defaults, overriding the default folder structure, and modifying Reem's behavior can all done within this JavaScript file.

Building

The command for building the source directory and writing to the output directory is plainly:

reem

Adventure Time!

Reem is a complex beast of unimaginable flexibility, performance, and developer joy. Now that you have her by your side and know how to fight with her, please sit down and read.

Reading

The Reem Wiki has official documentation, tutorials, and examples.

Plugins

  • reem-coffee compiles CoffeeScript files to JavaScript and supports source maps.
  • reem-draft hides unfinished posts from production builds.
  • reem-flow provides control structures for adding plugins to Reem.
  • reem-markdown converts Markdown to HTML.

More Reem plugins can be found on npm.

Contributing

Reem is a relatively new static site generator. To ensure the community their plugins will not potential break every day, Reem will strive to keep any and all changes backwards-compatible until the v1.0.0 release. So basically, v0 is being treated like v1.

Contributions are incredibly welcome. If you find an bug, open an issue. Feature requests are also welcome, but considering making a standalone plugin first. Any pull requests must pass the tests found in test/; if the pull does not pass, please explain why.

# running tests
npm run test