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

@ripl/node

v1.4.0

Published

Node.js runtime bindings for Ripl

Readme

@ripl/node

npm license size

The Node.js entry point for Ripl: renders scenes and charts to a terminal with no browser and no DOM emulation.

Features

  • Platform bindings on import — importing the package registers frame scheduling, performance.now, a device pixel ratio of 1, default drawing state, text measurement and element stubs, so @ripl/core runs off-browser without a DOM shim.
  • Re-exports @ripl/core and @ripl/terminal — one import gives you the elements, scene, renderer and the terminal context together.
  • createTerminalOutput() — a process.stdout-backed TerminalOutput. Resize subscribers are multiplexed behind a single SIGWINCH handler, so ten scenes do not trip Node's MaxListenersExceededWarning.
  • Terminal-accurate text metrics — measurement matches what the terminal actually paints (one braille cell per character, scaled by the requested font size), so a box does not jump between the first layout pass and the first frame.
  • Unref'd frame timer — the render loop never keeps an otherwise-idle process alive.
  • Charts included@ripl/charts draws through the same Context, so every chart type works from a script.

Installation

# npm
npm install @ripl/node

# yarn
yarn add @ripl/node

# pnpm
pnpm add @ripl/node

@ripl/core and @ripl/terminal arrive as dependencies and are re-exported, so this is the only package a terminal project installs. Add @ripl/charts for charts.

Quick start

import {
    createCircle,
    createContext,
    createTerminalOutput,
} from '@ripl/node';

const context = createContext(createTerminalOutput(), {
    logicalWidth: 800,
    logicalHeight: 600,
});

createCircle({
    stroke: '#38bdf8',
    lineWidth: 3,
    cx: 400,
    cy: 300,
    radius: 150,
}).render(context);

Key API

| Export | What it does | | --- | --- | | createTerminalOutput | A TerminalOutput backed by process.stdout | | createContext | The terminal context, re-exported from @ripl/terminal | | createScene / createRenderer | The scene graph and render loop, re-exported from @ripl/core |

Related packages

Documentation

Guides and the full API reference are at ripl.run/docs/core/contexts/node.

License

MIT