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

prompt-template-lite

v0.1.0

Published

Lightweight prompt templating with {{var}} interpolation and version tracking, so you know which prompt version produced which LLM output.

Readme

prompt-template-lite

Lightweight prompt templating with {{var}} interpolation and version tracking — so logs and evals can record exactly which prompt version produced which LLM output.

Install

npm install prompt-template-lite

Quick start

import { defineTemplate } from 'prompt-template-lite';

const summarize = defineTemplate('Summarize this in {{sentences}} sentences:\n{{text}}', { version: 'v3' });

const { text, version } = summarize.render({ sentences: 2, text: doc });
// log `version` alongside the LLM response so you can trace which prompt produced it

Missing a required variable throws immediately instead of silently rendering {{name}} into the prompt:

summarize.render({ text: doc }); // Error: Missing required template variable: "sentences"

Why version tracking matters

Prompt text changes constantly during development, and a model's behavior shifts with it. Without recording which exact prompt version produced a given output, you can't tell whether a regression in an eval run came from a model change, a prompt edit, or noise. defineTemplate auto-derives a version hash from the template text (or accepts an explicit one), and every render result carries it — cheap enough to log on every call.

API

  • defineTemplate(template, options?) — returns a PromptTemplate with .render(vars), .version, .source
  • .render(vars) — throws if a required {{var}} is missing, otherwise returns { text, version }

License

MIT