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

@dhruvhkumar19/imagizer

v0.1.0

Published

Render dense text into PNG pages for vision-capable coding agents.

Readme

IMAGIZER

IMAGIZER renders text into deterministic, high-contrast PNG pages for vision-capable coding agents. It is CLI-agnostic: output is simply page-*.png plus manifest.json.

Install

npm install
npm link

Requires Node.js 20+.

Render

imagizer render ./context.txt --out .imagizer/context
imagizer render - --out .imagizer/context --title "tool output" < output.txt

Options: --width, --height, --font-size, --line-height, and --title.

Each output directory contains lossless PNG pages and a manifest with the source byte count, SHA-256 digest, and render profile.

Use with coding CLIs

Attach the generated PNGs using your tool's normal image/file option. Keep the prompt short and tell the agent what the pages contain.

Claude Code

Attach page-*.png through Claude Code's image/file attachment workflow, alongside a prompt such as: Read the attached rendered context and implement the requested change.

OpenCode

OpenCode accepts file attachments in non-interactive mode:

opencode run --file .imagizer/context/page-001.png "Use this rendered context."

Repeat --file for each page. Verify the selected provider/model accepts image input.

Codex CLI

Codex CLI accepts initial image attachments:

codex --image .imagizer/context/page-001.png "Use this rendered context."

Repeat --image for more pages.

Other CLIs

Use any image or file attachment flag supplied by the CLI. If a tool only accepts text, IMAGIZER cannot reduce its text input directly; use that tool's multimodal API or a compatible provider.

Safety and quality

Image rendering is lossy. Keep exact values such as secrets, tokens, hashes, IDs, URLs, line-sensitive patches, and the current task as native text. Image only dense, older, low-risk context. Test your target model with realistic inputs before enabling automatic conversion.

PNG is the default because code and monospaced text remain sharp. JPEG and WebP are not recommended for dense code.

API

import { renderTextToImages } from "imagizer";

const { pages, manifest } = await renderTextToImages("large context", { width: 1536, height: 864 });
await writeFile("page-001.png", pages[0].png);

Development

npm test