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 🙏

© 2024 – Pkg Stats / Ryan Hefner

prompt-to-json

v0.0.10

Published

Call LLMs as a function

Downloads

10

Readme

prompt-to-json

Prompt LLMs with structured and reliable JSON response

Example

import { createPromptToJson, schema } from "prompt-to-json";

const promptRhymes = createPromptToJson({
  schema: schema.array(
    schema.string("A word that rhymes"),
    "A list of words that rhymes"
  ),
  sendPrompt: (prompt) => someLLM.completion.create(prompt),
  // Optionally add for more complex expectations of JSON response
  examples: [{ rhymes: ["ice", "spice"] }],
});

const { rhymes } = await promptRhymes("Give me 5 words rhyming with cool");

Why?

There are different kinds of LLM primitives:

  • Chat: Conversational, human to LLM
  • Assistant/Agent: Conversational, human to LLM with tools
  • Agentic worfklow: Conversational, human to LLM, LLM to LLM, with tools

prompt-to-json gives a lower level primitive that allows you to integrate LLMs in your existing application in a more targeted way. Send information to the LLM and get a predictable JSON response to populate your application state. You'll treat an LLM more like a way to generate data structures with values, than a conversation. I wonder if this low level abstraction could result in a different type of architecture than agentic workflows to do more complex tasks where LLMs is just one of many types of "functions".