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

@plurnk/plurnk-schemes-http-tavily

v1.19.1

Published

Tavily Extract page materialization for plurnk's http scheme — the third-party pluggability showcase.

Readme

@plurnk/plurnk-schemes-http-tavily

Tavily Extract page materialization for plurnk's http(s):// scheme — the documented showcase of third-party pluggability. This package owns zero scheme logic: it declares the http-materializer plugin family and implements the materializer contract that @plurnk/plurnk-schemes-http selects.

Install and enable

The package ships with the plurnk service as a default dependency, so an ordinary service install already carries it. To install it beside a service that does not:

npm install @plurnk/plurnk-schemes-http-tavily
# ~/.plurnk/.env, read by the service
PLURNK_SCHEMES_HTTP_MATERIALIZER=tavily-extract
TAVILY_API_KEY=...

A generic public HTML READ then keeps the exact server source as the page's body and lands the sanitized Tavily Markdown as its #readable channel; the entry header records the materializer identity and Tavily's request/usage evidence, and every READ of the page names #readable with its tokens. Without the selection (or the key), the installed HTML projection produces #readable instead, and the page reads the same way.

Configuration

| Variable | Contract | | --- | --- | | TAVILY_API_KEY | The Tavily API credential; absence makes the materializer ineligible | | PLURNK_SCHEMES_HTTP_TAVILY_DEPTH | basic or advanced | | PLURNK_SCHEMES_HTTP_TAVILY_TIMEOUT_MS | Positive request timeout in ms |

Contract

plurnk: { kind: "http-materializer", materializers: [{ id: "tavily-extract", module: "dist/materializer.js" }] } exports one HttpMaterializer (eligible/extract) under the framework's discovery, trust, and one-flat-id-namespace rules. See SPEC.md for the exact outcome mapping.

Develop

npm install   # links ../plurnk-service/plurnk-schemes-http for the plurnk-dev source
npm test