Exporting your module
When the course is ready, one command packages it for your LMS. The output is a ready-to-upload zip (or a plain website), self-contained, with nothing else to install or configure on the LMS side.
One command
pnpm export product-101Each course declares its export standard in its configuration, and the command produces the matching package:
| Standard | What ships |
|---|---|
| SCORM 1.2 | SCORM 1.2 package (zip) |
| SCORM 2004 | SCORM 2004 4th Edition package (zip) |
| cmi5 | cmi5 package, AU + manifest (zip) |
| xAPI | xAPI "Tin Can" package (zip) |
| Web | Static website, host anywhere |
The package lands in the course's own folder. A zip is named after the course title
and version, so a course titled "Product 101" at the default version exports to
courses/product-101/product-101-1.0.0.zip. A web export leaves the
built site in courses/product-101/dist/.
The package is self-contained: the runtime, your pages and media, and anything used from the shared design system are all inside. Validation and the accessibility checks run as part of the export, so a package that builds has passed validation and the blocking accessibility checks; remaining warnings, if any, are printed for you to weigh.
Same course, several LMSs
One flag re-packages the same course for a different standard, no changes to the course itself:
pnpm export product-101 --standard scorm2004Handy when one client's LMS wants SCORM 1.2 and another's takes cmi5: author once, export twice. Each export replaces the course's previous zip, so move the first one somewhere else before you run the second.
Test before you upload
SCORM Cloud has a free tier and plays all four LMS standards. Upload the zip, launch it as a learner would, and confirm the two things that matter: the course runs, and the LMS records what you expect (completion, score, per-question results) when you finish it.
| Standard | How to test |
|---|---|
| SCORM 1.2 / 2004 | Upload the zip to SCORM Cloud and launch it. |
| cmi5 | Upload to SCORM Cloud and launch via its cmi5 support. |
| xAPI | Upload to SCORM Cloud and launch; statements appear in its LRS view. |
| Web | No LMS needed; open the exported site in a browser. |
Upload to the real LMS
Use your LMS's normal course-import flow with the zip. One rule worth keeping: when you ship an updated version of a course whose structure changed, upload it as a new version or registration rather than overwriting in place. Learners' saved progress from the old structure can't be safely remapped to the new one, and Tessera deliberately starts them fresh instead of resuming them wrongly. The same happens when the update moves the course to a Tessera version that saves progress differently; the changelog says when a release does.