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

aywitb

v0.0.6

Published

This is the anything library, it does anything.

Downloads

11

Readme

aywitb

This is the anything library, it does anything.

bun add aywitb

Add the plugin to your bunfig.toml so generic types can be resolved at runtime:

preload = ["aywitb/plugin"]
import { aywitb } from "aywitb";

type WebSocketServer = {
  startServer({ port }: { port: number }): void;
  on(eventName: "verbose-log", handler: (event: unknown) => void): void;
}

const server = await aywitb<WebSocketServer>(`
  a websocket server that works with url-based rooms
  join by connecting to ws://.../room/{string[6]}
  rooms are upserted and messages fan to all clients in the room
`, { verbose: true });

server.on("verbose-log", console.log);
server.startServer({ port: 3000 });

Questions?

What does this actually do?

It takes the prompt you provide to the aywitb function, and runs it through a small, naïve and improvised pseudo-harness instructing the LLM to build the implementation.

Implementation is cached locally, if you change the prompt or generic - it will cache miss.

How do I run this?

With Bun, as a plugin component exists that pulls and resolves the generic type you pass into the aywitb function so inference can be ran with the type signature in the context.

When should I use this?

You shouldn't.

Is it safe to use?

No. If you do play with it, sandbox it.

Why did you make this?

I think I have an addiction to making things.