Import
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
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:
- Validates the source — Checks that the directory contains
slides.mdandpackage.json - Copies files — Transfers all presentation files to the
presentations/directory, excluding build artifacts and dependencies - Transforms package.json — Updates the package name to
@supaslidev/<name>, standardizes scripts, and adds@supaslidev/sharedas a dependency - Configures shared addon — Updates
slides.mdfrontmatter to include the@supaslidev/sharedaddon, giving you access to shared components and layouts - Installs dependencies — Runs
pnpm installto resolve workspace dependencies - Records the import — Tracks the imported presentation in workspace state
Excluded Files
The following files and directories are not copied during import:
| Pattern | Reason |
|---|---|
node_modules | Dependencies are reinstalled from workspace catalog |
.git | Git history is not transferred |
dist | Build output is regenerated |
.nuxt, .output | Framework cache directories |
| Lock files | Workspace uses its own pnpm-lock.yaml |
.DS_Store | System files |
Dependency Handling
Your presentation's existing dependencies are preserved as-is, with one exception: the vue dependency is normalized to catalog: so all presentations share the same Vue version from the workspace catalog. All other dependencies (including Slidev packages) keep their original versions. You can manually convert them to catalog: specifiers later if you want unified versioning.
Import from Dashboard
You can also import presentations through the dashboard UI:
- Press
⌘K(Mac) orCtrl+K(Windows/Linux) to open the command palette - Select Import
- Enter the path to your existing Slidev presentation (or comma-separated paths for multiple imports)
The import dialog also supports:
- Drag and drop: Drag a presentation folder directly onto the dialog
- Folder browser: Click the browse button to select a folder from your filesystem
- Validation preview: Each path is validated before import, showing the suggested name and any errors
- Progress tracking: A progress bar shows import status for batch imports
