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

promptdeploy

v0.1.2

Published

SDK for PromptDeploy — fetch and render versioned prompts at runtime

Readme

promptdeploy

JavaScript / TypeScript SDK for PromptDeploy — fetch and render versioned prompts at runtime.

Install

npm install promptdeploy

Quick start

import { PromptDeploy } from 'promptdeploy';

const pd = new PromptDeploy({
  apiKey: process.env.PROMPTDEPLOY_API_KEY,
  projectId: 'your-project-slug',
  env: 'production', // 'production' | 'staging' | 'development'
});

// Render a prompt server-side with variables
const text = await pd.render('welcome-email', {
  variables: { name: 'Alice', plan: 'Pro' },
});

// Fetch the raw template and render locally
const tmpl = await pd.get('welcome-email');
const text2 = tmpl.render({ name: 'Bob', plan: 'Free' });

API

new PromptDeploy(options)

| Option | Type | Default | Description | | ----------- | -------- | --------------------------------- | ----------------------------------------------------------------------------------------------------- | | apiKey | string | required | API key from your project settings | | projectId | string | — | Project slug. Recommended — the API will reject the request if the key belongs to a different project | | env | string | 'production' | Default environment to resolve prompts against | | cacheTtl | number | 60 | In-memory cache TTL in seconds | | cacheSize | number | 100 | Max cached entries | | baseUrl | string | https://api.promptdeploy.dev/v1 | Override for self-hosted instances |

pd.render(slug, options)Promise<string>

Renders a prompt server-side. Variables are interpolated by the API.

const text = await pd.render('onboarding', {
  variables: { userName: 'Alice' },
  env: 'staging', // override instance env for this call
});

pd.get(slug, options?)Promise<TemplateResult>

Fetches the raw template. Returns an object with:

  • template — raw template string
  • version — version number
  • env — resolved environment
  • render(variables, options?) — render locally (no network call)
  • extractVariables() — list variable names detected in the template
const tmpl = await pd.get('system-prompt');
console.log(tmpl.extractVariables()); // ['role', 'context']
const rendered = tmpl.render({ role: 'assistant', context: '...' });

pd.getTemplate(slug, options?)Promise<string>

Shorthand — fetches and returns just the raw template string.

Template syntax

Variables use {{double-brace}} syntax:

Hello, {{name}}! Your plan is {{plan}}.

Unknown variables throw by default. Pass strict: false to leave them as-is:

tmpl.render({ name: 'Alice' }, { strict: false });

Caching

Fetched templates are cached in memory (LRU). The cache is per-instance, so create one shared instance per process rather than per-request.

License

MIT