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

contextarea-context-worker

v0.0.2

Published

High level Requirements:

Downloads

4

Readme

Context Extraction Service

High level Requirements:

  • Strong focus on performance: KV-level initial response speeds.
  • For each link in the prompt, the frontend should have an api to render the context card for it which includes {url, title, tokens, ogImage, contentType, ...other}. these should be dynamically rendered below your prompt, and must be clear which belongs to which url somehow. when a prompt is pre-loaded, context cards may be pre-loaded from head JSON
  • Get the appropriate context for showing "context-cards" as well as for building context
  • Sanetize/DOMPurify?
  • Structured response: Invdividual URLs (url => object), but also think about string => array
  • Possibly separate in 2 apis: per item and for entire string.
  • ability to omitContext to just get details for api.

TODO

  1. Make this work as embeddable worker lib
  2. Use this in pastebin demo.html instead of doing the fetch in there (risking cors or other different results)
  3. Make demo into a js-lib (contextarea.js) so the HTML has full control over styling and page composition.
  4. In api, add result to window.data.context: object[]
  5. In both homepage.html and result.html use contextarea.js