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

@streavent/sv-runtime

v1.0.0

Published

Streavent Vibe Sites portable runtime (binder, registry, server render, data sources).

Readme

@streavent/sv-runtime

The runtime behind Streavent Vibe Sites — custom event websites, hand-built as plain HTML/CSS/JS and bound to live event data.

You write ordinary markup. <sv-*> elements and data-bind attributes mark the places where event data belongs. The same engine renders that markup on the server when the site is published, and hydrates it in the browser for interactive parts — so a preview on your laptop and the published site cannot drift apart.

This package is the tooling, not the starting point. To build a site, clone the starter: https://github.com/streavent/vibe-starter — it ships a complete example project, mock data, and the full contract (DESIGNER_CONTRACT.md).

Install

npm install --save-dev @streavent/sv-runtime

CLI

sv dev        # dev server with live preview and a contract report on every page
sv validate   # one-shot contract check, exit code 1 on errors (CI-friendly)
sv package    # validate, then zip src/ + streavent.config.json for upload

sv validate runs the same validator the Streavent platform runs when the bundle is uploaded. If it passes locally, it passes on upload.

Components

<sv-event> · <sv-speakers> · <sv-agenda> · <sv-sponsors> · <sv-events> · <sv-gallery> · <sv-capacity> · <sv-collection> · <sv-langswitch> · <sv-image>

Each list component takes your own <template> — there is no imposed markup or styling. The generated dist/COMPONENT_CATALOG.md and dist/custom-elements.json document every bindable field; editors that understand Custom Elements Manifest pick the latter up automatically.

Data source

By default the CLI renders against local mock-data/*.json, so a site can be built end to end without a backend. Pointing it at a real Streavent instance is opt-in:

VIBE_DATA_SOURCE=api \
VIBE_API_BASE_URL=https://api.streavent.de/api/app \
VIBE_EVENT_ID=<eventId> \
npx sv dev

Only public, already-published event data is read.

Browser bundle

The same components run standalone as custom elements, for embedding an agenda or speaker list on an existing site:

<script src="https://cdn.streavent.de/sv/v1/sv-runtime.js" defer></script>
<sv-agenda api-base="https://api.streavent.de/api/app" event-id="..."></sv-agenda>

sv/v1 is a stable major channel — patch releases land there automatically. Exact-version copies (sv/<version>/sv-runtime.js) exist for pinning.

License

MIT © Streavent UG (haftungsbeschränkt)