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

@haxtheweb/slide-deck

v0.0.0

Published

Present an imported PowerPoint deck slide by slide, with speaker notes

Readme

slide-deck

Presents a PowerPoint deck imported by HAXcms, slide by slide, in the page.

<slide-deck source="files/decks/my-talk/deck.json"></slide-deck>

The PPTX import route writes deck.json alongside the original file and its extracted media. That manifest is the element's only required input:

{
  "title": "My talk",
  "pptx": "files/decks/my-talk/original.pptx",
  "slides": [{ "number": 1, "title": "…", "html": "…", "notes": "…" }]
}

How it renders

Content is layered, so a deck degrades rather than breaks:

  • The manifest's per slide text and speaker notes always render. This is what assistive technology and site search read, and it is all that is needed for the deck to be navigable.
  • When the manifest names a pptx, the original file is painted over that text by @aiden0z/pptx-renderer. The renderer is only fetched once the deck scrolls into view, so a deck lower down a page costs nothing until it is looked at. If it cannot run, the text layer simply stays visible.

Properties

| property | attribute | description | | -------- | --------- | -------------------------------------------------------------- | | source | source | URL of deck.json, relative to the site or absolute | | deckId | deck-id | Distinguishes slide links when a page holds more than one deck | | slide | slide | Currently displayed slide, 1 based | | mode | mode | slide for one at a time, grid for every slide plus notes |

Slides are reachable by URL as #<deck-id>-slide-<n>, and arrow keys, Home and End move through a focused deck.

Commands

  • npm start - development server
  • npm run build - build and analyze
  • npm run test - run tests

Credits

A brighter future dreamed and developed by the Penn State HAXTheWeb initiative.