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

scorm-cli

v0.8.1

Published

Build SCORM 1.2 and SCORM 2004 packages from authored MDX content.

Readme

scorm-cli

Build SCORM 1.2 or SCORM 2004 packages from authored MDX content, with a local preview server.

Requirements

  • Node.js >=20.19.0.

Usage

# Build a SCORM 1.2 ZIP (writes dist/<content-name>.zip by default)
npx scorm-cli build ./content

# Choose the output path
npx scorm-cli build ./content --output ./build/package.zip

# Build a SCORM 2004 package (SCORM 1.2 is the default)
npx scorm-cli build ./content --scorm 2004

# Preview with a live-reloading local server
npx scorm-cli preview ./content --port 5173

build parses the content package, renders the static player, and writes a SCORM 1.2 ZIP by default. Use --scorm 2004 to create a SCORM 2004 ZIP. preview serves the same player with a mock LMS API and reloads as the content changes, reporting validation errors without stopping the preview. Preview uses the existing SCORM 1.2 development bridge; it does not emulate a SCORM 2004 LMS.

Authoring

Content packages declare their structure and components with typed markers imported from the scorm-cli/authoring subpath:

---
title: My Scroll Package
---

import { Scroll, Page } from 'scorm-cli/authoring'

<Scroll>
  <Page src="lessons/intro.mdx" />
  <Page src="lessons/one.mdx" />
</Scroll>

The import is inert: the CLI resolves the named bindings (and aliases) while parsing, but content files are parsed as data and never executed. See the repository README for the full authoring reference.

The authoring declarations reference React types, so @types/react is declared as an optional peer dependency: it is never installed automatically, but a project that provides it (as React projects already do) gets full type checking for the scorm-cli/authoring markers.

License

GNU General Public License v3.0 - see LICENSE for details.