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

richtemplate

v1.0.7

Published

***New Major Version Released!***

Readme

Javascript templating engine. Build Status

New Major Version Released!

Rewritten in es6, and also perfomance improvements.

Require module for parsing html files to plain Javascript. There is two environments, one Development another production.

Installation

using npm

npm install richtemplate

Why Templating Engine

Most javascript templating engines, parsing to string. Domtemplate has dom elements or require modules. You has direct access to Dom elements. In this case no need for jquery selectors etc.

How it works

Below is image to show difference between prod and dev packages.

Prod Dev Packages Diagram

In the development Environment you use runtime version of package, which one parse on browser. For Production you use compiled app version, where is no need for parser and coder.

Prerequisites

You need to install nodejs and grunt CLI globally npm -g install grunt-cli

How to install

Run

npm install

Then

grunt

How to use

Usage examples see in examples section.

Fix paths in require.config file

Templating parser use custom coders

Component - <cp></cp> use for require modules

<cp src="buttonA/buttonA" tp-name="testButton" ></cp>

Where

  • src is location of require Module
  • tp-name name of component. There also can be shortcut version

<cp-testButton src="buttonA/buttonA" ></cp-testButton>

-cp-testButton where testButton is the name of component

There can be used by only attributes as well

<div src="buttonA/buttonA" tp-type="cp" tp-name="testButton" ></div>

Placeholder - <pl></pl> use as containers in template, also can use in javascript as access to elements

<pl tp-name="testButton" tp-tag="h2" ></pl>

Where

  • tp-name name of Placeholder.
  • tp-tag tag of Placeholder, default value is div.

There also can be shortcut version

<pl-header ></pl-header>

  • pl-header where header is the name of placeholder

There can be used by only attributes as well

<h2 tp-type="pl" tp-name="header" ></h2>