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

no-drama-ollama

v0.1.5

Published

🦙 Minimalist web client for Ollama.

Readme

🦙 no-drama-ollama npm

Minimalist web client for Ollama which focuses on being easy to setup, run, and embed in your web application with a highly customizable appearance. Can also be used as a standalone app as well.

Basic setup

  • Install prerequisites:

    • Install Ollama to your system and ensure it is running.
    • Install Node.js. Both the current and LTS version of Node.js are supported. It is recommended to use a Node.js version manager like nvm or nvm-windows rather than the official installer, as a version manager will allow you to switch between multiple versions of Node.js easily.
  • Clone this repo.

  • Install dependencies:

    • Use npm ci if you're not altering the dependency list or changing the versions of your dependencies.
    • Alternatively, use npm install if you've altered the dependency list or changed the version of one of your dependencies. This is also necessary if you change the app's version number.
  • Run the app:

    • Use npm run production to run in production mode.
      • Available shorthands:
        • npm run prod
        • npm run p
        • npm start
    • Use npm run development to run in development mode.
      • Available shorthands:
        • npm run dev
        • npm run d
    • Use npm run production-proxy to run the app in production mode, but with localhostOnly set to true and hostPublic set to false. This mode will make it so your app only listens to requests coming from localhost and does not serve anything in the public folder. This mode is useful when you want to host your app behind a reverse proxy from a web server like Apache or nginx and is considered a best practice for Node.js deployments.
      • Available shorthands:
        • npm run prodproxy
        • npm run x
    • See docs for more information about configuring and running Roosevelt apps.

Customize deployment

To set a global system prompt to provide the model context to use before answering, set the environment variable NO_DRAMA_OLLAMA_CONTEXT_FOLDER to a directory containing markdown (*.md) files with instructions for the model.

Integrating into other web apps

There are many ways to integrate no-drama-ollama into your web application.

One relatively straightforward way is to start no-drama-ollama as a child process from within your app, then proxy chat requests to the no-drama-ollama child process. See the sample app for a demo of how to do that in Node.js.

Another way to do it would be to run no-drama-ollama as a separate web service and use another web server to create a reverse proxy on the appropriate URLs instead of doing it from within your main application.