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

content-generation-example

v0.1.0

Published

Multi-format content generation pipeline — research, draft, 4 parallel formats, optional translate

Readme

Multi-Format Content Generation

Generates 4 content formats simultaneously from a single topic using flomatai's parallel step. Research a topic once, produce a blog post, Twitter thread, LinkedIn post, and TL;DR newsletter snippet in parallel, with optional translation.

Pipeline Graph

research-topic
    ↓
parallel (all 4 formats at once):
  ├── format-blog      → blog post (600+ words, markdown)
  ├── format-twitter   → thread (5-8 tweets, ≤280 chars each)
  ├── format-linkedin  → post (1300-1800 chars, professional)
  └── format-tldr      → snippet (headline + 3 bullets + takeaway)
    ↓
[optional] translate-content (--translate-to <language>)

Setup

cp .env.example .env
# Fill in ANTHROPIC_API_KEY (or OPENAI_API_KEY)
pnpm install
pnpm build

Usage

# Generate all 4 formats for a topic
node dist/src/run.js --topic "The future of AI automation"

# With audience and tone guidance
node dist/src/run.js \
  --topic "TypeScript generics explained" \
  --audience "junior developers" \
  --tone "educational and friendly"

# With translation
node dist/src/run.js \
  --topic "Remote work best practices" \
  --translate-to "Spanish"

# Custom output directory
node dist/src/run.js --topic "..." --output ./my-content

Output Files

All files are saved to ./output/ (or --output path):

| File | Description | |------|-------------| | <slug>-blog.md | Long-form blog post in Markdown | | <slug>-twitter.md | Twitter thread (numbered tweets) | | <slug>-linkedin.md | LinkedIn post ready to publish | | <slug>-tldr.md | Newsletter snippet | | <slug>-blog-<lang>.md | Translated blog (if --translate-to set) |

Environment Variables

| Variable | Description | |----------|-------------| | ANTHROPIC_API_KEY | Anthropic API key | | OPENAI_API_KEY | OpenAI API key (alternative) | | OPENCODE_BASE_URL | Use local OpenCode proxy | | OUTPUT_DIR | Output directory (default: ./output) |