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

common-hjs

v0.2.0

Published

Compiles hogan templates into html using a common base template

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

mattstylesmattstyles

Keywords

hoganhjscommontemplatetemplatingwatch

Readme

common-hjs

Collects up partials and layouts and punts them through a base template

Getting Started

npm i common-hjs
hulk compile -b src/views/base.hjs \
  -d data.json \
  -p 'src/{common,bundles}/**/*.hjs' \
  -o dist

This will compile the templates, using base.hjs as a base, it will then search the glob specified with -p for index.hjs files to use as layouts and everything else will become a partial for use within the base or the layouts. -d specifies the data to render the templates with.

## Example

.
└── src
    ├── bundles
    │   ├── bundleA
    │   │   ├── component.hjs
    │   │   └── index.hjs
    │   └── bundleB
    │       └── index.hjs
    ├── common
    │   └── header.hjs
    └── views
        └── base.hjs

Given this file structure the templates would get grouped like this:

// Partials
component
header

// Layouts
bundleA/index
bundleB/index

// Base
base

The filenames are currently important and partials should have unique names or common-hjs will complain when trying to compile them. The layouts are all called index but this doesn’t matter because they get added to the partials as a body only when rendering the base template. Currently only one base can be specified per compile.

<!-- base -->
<body>
  {{> header }}
  <h1>Base</h1>
  {{> body }}
</body>
<!-- bundleA -->
<section>
  <h2>Bundle A</h2>
  {{> component }}
</section>
<!-- bundleB -->
<section>
  <h2>Bundle B</h2>
</section>

These file contents would all render out pretty much as you would probably expect, where bundleA and bundleB get inserted as the body and all the other partials use their naked filename to include them.

Putting partials inside bundles is incredibly useful and having this naming restriction is pretty rubbish, so that’s on the todo list. For now a bit of namespacing and you’re all good.

Templates can be accessed from anywhere so they’re effectively global, ditto for the data you’re passing in. Another roadmap item is merging json files to allow some data separation, pull requests welcomed.

Enjoy responsibly!