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

@rudderjs/terminal

v1.1.2

Published

Laravel-style `terminal('id', props)` for the terminal — the same ergonomics as `view()`, but renders React/Ink components in the CLI instead of Vike pages in the browser.

Readme

@rudderjs/terminal

Laravel-style terminal('id', props) for the terminal — the same ergonomics as view(), but renders React/Ink components in the CLI instead of Vike pages in the browser.

Installation

pnpm add @rudderjs/terminal react

Usage

1. Create a terminal component

Generate with the scaffolder:

pnpm rudder make:terminal Dashboard

Or create manually in app/Terminal/Dashboard.tsx:

import React from 'react'
import { Box, Text, useApp } from 'ink'

interface DashboardProps {
  appName: string
}

export default function Dashboard({ appName }: DashboardProps) {
  const { exit } = useApp()

  React.useEffect(() => {
    const t = setTimeout(() => exit(), 100)
    return () => clearTimeout(t)
  }, [exit])

  return (
    <Box padding={1}>
      <Text bold>{appName}</Text>
    </Box>
  )
}

2. Register a rudder command

// routes/console.ts
import { Rudder } from '@rudderjs/console'
import { terminal } from '@rudderjs/terminal'

Rudder.command('dashboard', async () => {
  return terminal('dashboard', { appName: 'MyApp' })
}).description('Show the dashboard')

3. Run it

pnpm rudder dashboard

Component discovery

| terminal(...) call | File resolved | |------------------------------|---------------------------------------| | terminal('dashboard') | app/Terminal/Dashboard.tsx | | terminal('admin.users') | app/Terminal/Admin/Users.tsx | | terminal('auth.login') | app/Terminal/Auth/Login.tsx |

Notes

  • Requires an interactive TTY — throws a clear error in CI or piped output
  • Components must have a default export
  • Use useApp().exit() from Ink to signal completion; omit it for long-running interactive UIs that exit on Ctrl+C
  • react is a peer dependency — already present in vike-react apps