Supaslidev Logo
Features

Import

Import existing Slidev presentations into your Supaslidev workspace.

Single Presentation Import

Import a presentation from your local filesystem using the CLI:

pnpm supaslidev import /path/to/my-presentation

By default, the imported presentation uses the source directory name. Specify a custom name with the --name flag:

pnpm supaslidev import /path/to/my-presentation --name quarterly-review
Presentation names must be lowercase alphanumeric with hyphens only (e.g., my-presentation, q4-2024-review).

Skipping Dependency Installation

By default, import runs pnpm install after copying files. Skip this step if you want to install dependencies later:

pnpm supaslidev import /path/to/my-presentation --no-install

Batch Import

Import multiple presentations by running the import command for each source directory:

pnpm supaslidev import /path/to/presentation-one
pnpm supaslidev import /path/to/presentation-two
pnpm supaslidev import /path/to/presentation-three

Use the --no-install flag on all but the last import to avoid redundant dependency installation:

pnpm supaslidev import /path/to/presentation-one --no-install
pnpm supaslidev import /path/to/presentation-two --no-install
pnpm supaslidev import /path/to/presentation-three

What Happens During Import

When you import a presentation, Supaslidev:

  1. Validates the source — Checks that the directory contains slides.md and package.json
  2. Copies files — Transfers all presentation files to the presentations/ directory, excluding build artifacts and dependencies
  3. Transforms package.json — Updates the package name to @supaslidev/<name> and standardizes scripts
  4. Installs dependencies — Runs pnpm install to resolve workspace dependencies
  5. Records the import — Tracks the imported presentation in workspace state

Excluded Files

The following files and directories are not copied during import:

PatternReason
node_modulesDependencies are reinstalled from workspace catalog
.gitGit history is not transferred
distBuild output is regenerated
.nuxt, .outputFramework cache directories
Lock filesWorkspace uses its own pnpm-lock.yaml
.DS_StoreSystem files

Dependency Conversion

Your presentation's dependencies are preserved, but Slidev core packages are resolved through the workspace catalog. This ensures consistent versions across all presentations and simplifies updates.

Import from Dashboard

You can also import presentations through the dashboard UI:

  1. Press ⌘K (Mac) or Ctrl+K (Windows/Linux) to open the command palette
  2. Select Import
  3. Enter the path to your existing Slidev presentation

Next Steps

Dashboard

Quick Start