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

@paulkinlan/f

v0.1.1

Published

Natural Language to runnable functions.

Readme

f

Natural Language to runnable functions.

import { create } from "@paulkinlan/f";
import { prompt, ChromePromptConfiguration } from "@paulkinlan/reactive-prompt/chrome"

// Create the builder - we have to tell it which reactive prompt we want to use.
const config = new ChromePromptConfiguration();
const f = create(
  prompt, config
);

// Create a function that sums two numbers
const sum = await f`Sum two numbers`;

console.log(sum(22,44)) // Run the code.

Using Claude (or other LLMs)

reactive-prompts offers the developer to use the following LLMs:

  • Gemini - import { prompt, GeminiPromptConfiguration } from "@paulkinlan/reactive-prompt/gemini
  • Gemini Nano in Chrome - import { prompt, ChromePromptConfiguration } from "@paulkinlan/reactive-prompt/chrome
  • Claude - import { prompt, ClaudePromptConfiguration } from "@paulkinlan/reactive-prompt/claude
  • OpenAI - import { prompt, OpenAIPromptConfiguration } from "@paulkinlan/reactive-prompt/openai
  • Ollama - import { prompt, OllamaPromptConfiguration } from "@paulkinlan/reactive-prompt/ollama

You can pass in the exported prompt and configuration objects in to create and f will use these libraries as the LLM exectution engine.

Recompiling the function

Because the prompting library is based on reactive-prompts it is possible to recompile the function when the prompt uses a signal to change the prompt.

import { create } from "@paulkinlan/f";
import { prompt, ChromePromptConfiguration } from "@paulkinlan/reactive-prompt/chrome";
import { signal, effect } from "@preact/signals";

const f = create(
  prompt, new ChromePromptConfiguration()
);

const numbers = signal(2);

// Prompts can take a signal as an argument which means the prompt can re-run.
const sum = await f`Sum ${numbers} numbers`;

// The first generated function is the direct invocation of the code generated by the prompt. While it can update, you won't know if it did.
console.log("Direct invocation", sum(22,44));

// Update the signal which will re-generate the function.
setTimeout(() => {
  numbers.value = 3;
}, 2000);

// Watch for changes.
effect(()=>{
  // Each function has a signal that you can watch.
  const func = sum.signal.value;
  // You can either call sum directly, or you can do it via the signal.
  if (func) {
    if (func.length === 2) {
      console.log(func(22, 44));
    } else if (func.length === 3) {
      console.log(func(1,2, 3));
    }
  }
})

Installation

npm install @paulkinlan/f