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

@lossless-group/dididecks-player

v0.1.0

Published

DidiDecks player: 16:9 slide canvas, play deck, scroll deck, chrome, paginator and print layout for Astro. Static components, scoped CSS, no Tailwind.

Readme

@lossless-group/dididecks-player

The viewer half of DidiDecks: everything needed to show a deck, nothing needed to author one.

Static Astro components with scoped CSS, themed by --ddd-chrome-* tokens. No Tailwind, no filesystem access, no registry, no Reveal.js. Slides are plain HTML/CSS at a 1920×1080 design size; the player scales them to any screen in pure CSS and prints them one per page.

What's new in 0.1.0

The first release: the viewer half of DidiDecks, out of the authoring shell and into its own package, chosen from nine drifting copies across the Lossless tree.

  • DeckPlayer + PlayerSlide: a single-page player. One 16:9 slide at a time, arrow keys and swipe, T/J for a contents list that skips to any slide, F for fullscreen, #N links, and ⌘P prints one slide per page.
  • SlideCanvas centres its slide, so letterboxing is even on both sides.
  • DeckChrome knows where you are: it listened for an event the scroll deck never sent. Cmd, Ctrl and Alt shortcuts now pass through to the browser.

Full notes: changelog/releases/0.1.0.md · GitHub release

Install

pnpm add @lossless-group/dididecks-player

Peer dependency: astro 6 or later.

What's in it

| Component | What it does | |---|---| | DeckPlayer + PlayerSlide | Single-page play deck: one 16:9 slide at a time; ← → / Space / PageUp PageDown / Home End; swipe; T or J for a contents list that skips to any slide; F fullscreen; #N links to a slide; ⌘P prints every slide, one per page | | SlideCanvas | Scales a 1920×1080 stage to any container with container queries (no JS), centred and letterboxed. Optional wash layer via --slide-backdrop-* | | ContentFit | Opt-in island that scales overflowing content down to fit its box | | PageAsDeckWrapper + SlidePaginator | Scroll deck: scroll-snap sections, keyboard and double-click navigation, an NN / total indicator with type-to-jump | | DeckChrome | Floating navigation capsule for multi-page play routes | | ModeToggle + runtime/mode-switcher.ts | light / dark / vibrant on html[data-mode] | | PrintDeck | Print layout: each child is one landscape page |

Use

---
import DeckPlayer from "@lossless-group/dididecks-player/components/DeckPlayer.astro";
import PlayerSlide from "@lossless-group/dididecks-player/components/PlayerSlide.astro";
import Cover from "../slides/Cover.astro";
---
<DeckPlayer title="Firm deck" pdfHref="/firm-deck.pdf" backHref="/decks/">
  <PlayerSlide title="Cover"><Cover /></PlayerSlide>
  <PlayerSlide title="Portfolio" image="/slides/11.jpg" />
</DeckPlayer>

A PlayerSlide takes either inline content (an Astro component authored at 1920×1080) or an image (a rendered snapshot of a slide). Both scale the same way.

Contracts

  • Events. Play and scroll decks emit deck:section-changed { index, total, isFirst, isLast } on window, and respond to deck:section-goto { index }, deck:section-prev and deck:section-next.
  • Theming. Components read only --ddd-chrome-* tokens (styles/chrome-tokens.css), which fall back to a site's own --color-* and --font-* tokens. Override them at any wrapping element.
  • Keyboard. Cmd, Ctrl and Alt chords always pass through to the browser. Keys are ignored while typing in an input.
  • Slides stay static. No script runs inside a slide; the player's own script handles navigation.

What isn't here

The authoring side of DidiDecks stays in @dididecks/shell in dididecks-ai: the slide rater and triage tools (they write to the filesystem and are dev-only), the deck registry, and the injected /play and /toc routes. The shell depends on this package and re-exports these components at their old paths.

Docs

License

MIT