@maxedapps/mslides

Substantive package for source-first React presentations: runtime player APIs, mslides CLI (list|view|add|create), bundled official registry, and project creator.

Runtime

import { Player, createSlides, type SlideModule } from "@maxedapps/mslides"
import "@maxedapps/mslides/style.css"

const modules = import.meta.glob<SlideModule>("./presentation/*.tsx", { eager: true })
const deck = createSlides(modules)

<Player
  slides={deck}
  basePath={import.meta.env.BASE_URL}
  motion={{ transition: { preset: "fade-through", duration: 500 } }}
/>

Slides compose Slide, Reveal, Disappear, Highlight, Emphasis, RevealSequence, and RevealItem. Public transition presets are none, fade, fade-through, slide, push, cover, reveal, zoom-in, and zoom-out.

Direct production routes require the host to rewrite unknown presentation paths to index.html.

Create a project

npm create mslides@latest my-presentation

npm launches the thin create-mslides package, which forwards to this package's canonical mslides create command with its exact pnpm executable. Generated projects use pnpm and depend only on @maxedapps/mslides.

Alternatives:

pnpm create mslides@latest my-presentation
pnpm dlx @maxedapps/mslides@latest create my-presentation

Registry CLI

pnpm mslides list [--type <type>]
pnpm mslides view <name>
pnpm mslides add <name...> [--overwrite]
pnpm mslides create [directory]
pnpm mslides --help
pnpm mslides --version

mslides.json schema path after install:

{
  "$schema": "./node_modules/@maxedapps/mslides/schema/mslides.schema.json"
}

Package surface

• Exports: . (runtime ESM + types) and ./style.css only.
• Bin: mslides
• Files: runtime dist, Node CLI/create dist, bundled registry, template/skill bundle, schema.
• Peers: react ^19.2.0

There is no bare mslides npm package. create-mslides is only the npm initializer; the agent skill remains the separate file/mvault identity at skills/create-mslides / .agents/skills/create-mslides.