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

wiki-plugin-stage

v0.1.0

Published

Federated Wiki plugin — present an HTML asset or inline standalone HTML fullscreen, from a relative /assets path, an absolute URL, or HTML pasted into the item itself (travels with the fork)

Readme

wiki-plugin-stage

A Federated Wiki plugin that presents an HTML asset or inline standalone HTML fullscreen — slides, dashboards, visualisations — from a relative /assets path, an absolute URL, or HTML pasted into the item itself, which travels with the fork.

Item syntax

UPPERCASE directives first, one per line, then the body:

ASSET deck.html          serve from the page's own /assets folder
HTML  https://…          or an absolute URL
IMPORT https://…         fetch once and inline the HTML into the item
POSTER cover.png         click-to-load poster image
RATIO 4/3                aspect ratio (default 16/9)
TITLE My Deck            caption in the bar

<h1>…or paste standalone HTML here…</h1>

Trust model

  • Inline/embedded HTML is sanitised with DOMPurify and rendered in an iframe with sandbox="" — no scripts, ever.
  • Referenced assets run with sandbox="allow-scripts allow-popups allow-popups-to-escape-sandbox" and no allow-same-origin, so they cannot read the wiki's cookies or storage. Note the deliberate tradeoff: a hostile referenced asset can open an unsandboxed popup.
  • An un-sandboxed TRUST mode is intentionally not implemented, pending identity and code signing.

Install

npm install wiki-plugin-stage

Restart the wiki server so the factory and the bundled about page register.

Develop

npm install
npm run build   # esbuild bundle into client/
npm test        # node --test over the pure parse/build helpers

License

MIT © David Bovill