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

@0xhoneyjar/quests-engine

v0.1.2

Published

Headless quest engine — substrate-step dispatch bridging (gateway → construct → resolution) + future quest publish/query/complete/claim flows. Framework-agnostic. The construct is OPENED via Effect Requirements; consumers plug in their own grader.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

janitooorjanitooorzerkerethzerkerethzksojuzksoju

Keywords

freesidequestsengineeffectstate-machine

Readme

packages/engine — headless quest logic

The core quest engine library. Stateful where needed; framework-agnostic. What cubquests-dashboard/actions/* becomes when the operator-dashboard chrome is stripped from the engine logic.

Status: scaffolded; content extraction pending

Source: world-sprawl/cubquests-dashboard/actions/ + world-sprawl/cubquests/apps/frontend/lib/. Per ../../docs/EXTRACTION-MAP.md.

Planned contents (post-extraction)

| file | purpose | |---|---| | publish.ts | Quest publishing flow (validate, persist via injected port, emit completion event). Logic only; DB binding is swappable. | | queries.ts | Cached quest queries; cache layer parameterized. | | loader.ts | Quest discovery + filtering logic. | | generators.ts | Quest authoring helpers (generate-input + generate-json + diff utilities). | | diff.ts | Quest-version diff utility (find-json-differences). | | claim/ | Consumer-side claim flow (validate completion, mint badge, emit event). Currently inline in cubquests' apps/frontend/lib/. | | index.ts | Public exports |

Why "headless"

The engine has logic that operates on schemas + ports. It does NOT:

  • Render UI (that's packages/ui/)
  • Talk directly to a specific DB (that's adapter-injected)
  • Know about Next.js / SvelteKit / framework specifics
  • Own the partner integrations (those stay in CubQuests)

This makes the engine reusable: any app (Purupuru, Honey Port, Mibera, future) can install + wire up the engine to its own UI + DB + chain integrations.

Composition

  • Imports types + schemas from ../protocol/
  • Implements ports declared in ../ports/
  • Doesn't import ../ui/ (rendering is downstream)
  • Doesn't import ../adapters/ (adapters compose with the engine; engine doesn't depend on transport)

Consumers

  • world-sprawl/cubquests-dashboard/ — post-extraction, dashboard wires its actions to call engine functions instead of inline logic
  • world-sprawl/cubquests/apps/frontend/ — claim flows wire to engine/claim/
  • Future world apps (Purupuru Year 2, Honey Port) — install + wire up the engine
  • Server-rendered surfaces that want quest data without a roundtrip