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

ollamer

v1.0.2

Published

Ollama wrapper to create function-like prompts

Readme

ollamer

What is ~~love~~ ollamer?

Minimalistic wrapper for ollama for your experiments with building workflows locally.

Build your prompts with JSON output and use them as regular async functions.

Usage example

Create folders with your prompts:

src
  tasks
    check_relevance
      index.ts
      article.hbs
  index.ts

Create ollama task.

// src/tasks/summarize/index.ts
import joi from 'joi';
import { resolve } from 'node:path';
import { createTask } from 'ollamer';

// argument for our function
export type Input = {
  title: string;
  article: string;
};

// expected output format for out function
export type Relevance = {
  related: boolean;
  confidence: number;
  reason: string;
};

export default createTask<Input, Relevance>({
  model: 'llama3.2',

  name: 'check_relevance',

  options: {
    // Ollama's options
    temperature: 0.1,
  },

  retries: 1,

  timeout: 30 * 1000,

  // Use `format` field to create JSON typing (it will be verified)
  format: joi.object<RelevanceResult>({
    related: joi.boolean()
      .required(),
    confidence: joi.number()
      .min(0)
      .max(1)
      .required(),
    reason: joi.string()
      .required(),
  }),

  templates: [
    {
      role: 'system',
      filename: resolve(import.meta.dir, './system.hbs'),
    },
    {
      role: 'user',
      filename: resolve(import.meta.dir, './article.hbs'),
    },
  ],
});

Use this task as it is usual asynchronous function:

// src/index.ts
import summarizeTask, type { Input, Relevance } from './tasks/summarize';
import type { Result } from 'ollamer';

const title = 'Using Ollama never was so convenient!';
const article = ` ... your articles are beautiful ... `;

const result: Result<Input, Relevance> = await summarizeTask.run({
  title,
  article,
});

console.log(result.output); // type defined with your Joi schema

That's it. Read package's JSDocs for more details.