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

rpgterm-engine

v0.1.2

Published

Pure logic engine of the Immersive Terminal for RPGs: virtual filesystem, command interpreter, crack/tracer/decrypt mechanics, scenario composition. No DOM, no React.

Readme

rpgterm-engine

npm license

Motor de lógica pura do Immersive Terminal for RPGs, extraído para ser fonte única — consumido tanto pelo terminal quanto pelo editor scenario-forge, acabando com o risco de divergência de schema entre quem cria os cenários e quem os roda.

Sem DOM, sem React, sem áudio. ESM puro. O host injeta áudio e persistência via ctx.

Instalação

npm install rpgterm-engine

Pacote ESM-only. Importe com import (não require). Ele importa JSON internamente, então rode-o por um bundler (Vite/webpack/Rollup) ou por um runtime com suporte a JSON modules — em Node puro use --experimental-json-modules quando aplicável. No Vitest, os consumidores precisam de test.server.deps.inline: [/rpgterm-engine/] para o engine ser transformado dentro de node_modules.

Conteúdo

  • Sistema de arquivos virtual (normalizePath, getNode, listDir, buildFilesystem)
  • Interpretador de comandos (runCommand, complete) — ls/cd/cat/crack/decrypt/unlock/check…
  • Mecânicas: crack (força bruta / DC), tracer & recon (effTracer, scanTier), decrypt estilo Wordle (scoreGuess, pickWord, isWin, rollLuck)
  • Cenários (parseFrontMatter, composeCustomScenario) + os 8 skins de tema (THEMES, THEME_REGISTRY)
  • Markdown → linhas (renderMarkdown)
  • Compartilhamento (encodeBundle, decodeBundle, shareUrl)
  • i18n (makeT, SUPPORTED_LANGS)

A superfície pública completa (com tipos) está em src/index.d.ts.

Uso

import { composeCustomScenario, runCommand } from 'rpgterm-engine'

const bundle = {
  theme: 'cprd',
  id: 'demo',
  files: { '/intel/blackbox.dat': '---\nlocked: true\npassword: OPEN\n---\nsegredo' },
}

// Monta o cenário no formato que o terminal renderiza (fs virtual + tema).
const scenario = composeCustomScenario(bundle)

Áudio / persistência (opcional)

Os comandos volume e hum usam ctx.audio (adaptador injetável) e ctx.persist(key, value). Sem eles, funcionam como no-op — ideal para preview e testes. Exemplo de ctx mínimo para runCommand:

const ctx = {
  fs,                         // Vfs (de buildFilesystem)
  cwd: '/',
  theme,                      // skin de THEME_REGISTRY
  t: makeT('pt'),             // tradutor
  unlock: (path) => { /* … */ },
  // audio / persist são opcionais
}
runCommand('ls', ctx)

Onde é usado

  • Immersive Terminal for RPGs — o terminal jogável (UI React em cima deste motor).
  • scenario-forge — editor desktop que monta os cenários; tem um teste de paridade rodando contra este pacote, garantindo que o que o editor exporta é exatamente o que o terminal lê.

Dev

npm install
npm test          # vitest run
npm run test:watch

Publicação

npm version <patch|minor|major> e empurrar a tag (git push --follow-tags) dispara o workflow publish.yml, que roda os testes e publica no npm via NPM_TOKEN.

Licença

MIT © Felipe Lippelt