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

@kopflos-labs/html-template

v0.1.0

Published

Renders `<template>` elements in kopflos but running their contents in a templating library.

Readme

Template processor for kopflos

Renders <template> elements in kopflos but running their contents in a templating library.

Usage

Add to a handler chain to process templates.

Two parameters are required:

  1. A (template: string, graph: MultiPointer): string function delegate
  2. The URL of the resource to render (⚠️ This is bound to change soon ⚠️)

The function is called for every <template> element in the document, bottom up. The HTML contents of the <template> element are passed as the template parameter. The graph parameter is a clownface object representing the resource to render. The node which it represents depend on the nesting of the <template> elements.

[
  a kl:ResourceShape ;
  kl:handler
    [
      a kl:Handler ;
      kl:method "GET" ;
      code:implementedBy
        (
          # ...previous handlers to prepare the template...
          [
            a code:EcmaScriptModule ;
            code:link <node:@kopflos-labs/html-template#default> ;
            code:arguments
              (
                [ a code:EcmaScriptModule; code:link <node:@kopflos-labs/handlebars#default> ]
                "${uri}"^^code:EcmaScriptTemplateLiteral
              ) ;
          ]
        )
    ] ;
] .

Templating libraries

Writing templates

Target Class

The target-class attribute on the <template> element is used to select resources to render from the graph.

The value can be a relative URL, which will be resolved against the API's base IRI.

<!DOCTYPE html>
<html lang="en">
<body>
  <template target-class="/api/schema/Plaque">
    <!-- use a templating library to render instances of /api/schema/Plaque -->
    <div>
      <h1>{{ schema:name }}</h1>
    </div>
  </template>
</body>
</html>

Property Paths

A <template> element with property attribute is used to drill down into the graph.

<!DOCTYPE html>
<html lang="en">
<body>
  <template target-class="/api/schema/Plaque">
    <template property="schema:image">
      <!-- here the context changes to the image of the plaque resource -->
      <img src="{{ schema:url }}" />
    </template>   
  </template>
</body>
</html>