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

farplotzy

v1.0.2

Published

Server-rendered plots for React

Readme

Farplotzy

Server-rendered plots for React.

The browser never draws anything. You describe the plot, the component posts that description to the render backend, and the backend sends back a finished image. A 200,000-point scatter plot costs the client exactly what a bar chart costs: one request and one <img>.

Farplotzy is commercial software. See LICENSE.

Install

npm install farplotzy

Activate

The package ships inactive. One binary turns it on:

/bin/cli-http-linux

There is no account, no signup, and no password. Activation generates a random UUID for this install, posts it to the activation service, and gets a render token back. The CLI prints the exact request body before sending it:

That is everything that leaves your machine. The install id is random — it is not derived from your hostname, username, or hardware, so it says nothing about the machine it came from. Nothing else on disk is read.

<Plot /> shows a placeholder while the image renders, aborts the request if the spec changes mid-flight, and revokes the object URL on unmount. Any extra props go straight to the <img>.

Outside React, or on the server:

const { renderPlot } = require('farplotzy');

const url = await renderPlot(
  { type: 'bar', data: { x: ['a', 'b'], y: [3, 7] } },
  { token: process.env.FARPLOTZY_TOKEN }
);

API

<Plot />

| Prop | Type | Description | | --- | --- | --- | | type | string | line, bar, scatter, heatmap | | data | object | Series data, shape depends on type | | options | object | Title, size, axes, theme | | token | string | Overrides FARPLOTZY_TOKEN | | endpoint | string | Overrides the default render backend | | alt | string | Alt text; defaults to "<type> plot" |

renderPlot(spec, opts)

Returns a Promise<string> — an object URL for the rendered image. Revoke it yourself when you're done. Accepts {endpoint, token, signal}.

Self-hosting

Point both services at your own infrastructure:

FARPLOTZY_ACTIVATION_URL=https://licence.internal/v1/activate npx farplotzy activate
<Plot endpoint="https://plots.internal/v1/render" ... />

Development

npm test

License

Commercial. See LICENSE.