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

flingit

v0.0.15

Published

Personal Software Platform - Build and deploy personal tools through conversation

Readme

Fling

Small Software Platform — Build and deploy small apps and tools through conversation.

Watch the demo

What is Fling?

Fling is the fastest way from Claude Code to deployed software.

"I want a podcast feed that picks randomly between Hard Fork and The Daily each day, and gives me one episode per day."

Claude writes the code, runs it locally, tests it, and iterates until it works. You can watch the local server, see logs, check the database — but you don't have to.

The target user is anyone who can describe what they want. Technical users get the benefit of standard, portable code. Non-technical users get things built without knowing that code exists.

Quick Start

npx flingit

That's it. This creates a project at ~/fling, sets up the environment, and opens Claude Code. You're immediately in a conversation — just describe what you want to build.

Requires Node.js 22 or later.

Principles

  • Small Software
  • Super low friction
  • You own the agent
  • Batteries included

How It Works

Fling provides four primitives (more to come) that Claude uses to build your tools:

| Primitive | What it does | |-----------|--------------| | HTTP | Expose endpoints to the web (via Hono) | | Cron | Run code on a schedule | | Database | Store and query data (SQLite) | | Secrets | Manage API keys and credentials |

Everything works locally during development. When you're ready, just tell Claude Code to deploys to production.

Design Philosophy

  1. Claude-first, not CLI-first — The user's interface is natural language. The CLI exists for Claude to operate.

  2. Standard tools over custom abstractions — Hono for HTTP, SQLite for data, standard cron syntax. Claude already knows these.

  3. Local-first development — Everything works and can be tested locally.

  4. Fail fast — Missing secrets throw. Invalid syntax throws. Obvious errors help Claude debug.

Running Fling From Source

To run fling from this repo, just do

npm run cli

That's the equivalent of running npx flingit. It will also do the onboarding flow and create a Fling project, but the flingit dependency there will point to your local package instead of the public package on NPM.

Publishing

The package is published to npm as flingit. The prepublishOnly script runs lint, typecheck, build, and tests automatically.

npm publish

To do a dry run first:

npm pack --dry-run

Documentation