Export to your LMS¶

Clipboard icons

Commands and prompts on this page use fenced blocks with a copy button (top-right). Click to copy the full text for Terminal, Claude, or Cursor.

Build creates the file your LMS imports. Choose a target that matches what your LMS and reporting team require.

Choose a target¶

Target	When to use
`scorm12`	Default for most corporate LMS (Moodle, Cornerstone, etc.)
`scorm2004`	LMS requires SCORM 2004 multi-activity or sequencing
`xapi`	Tin Can / xAPI to an LRS; needs HTTPS activity IRI
`cmi5`	LMS supports cmi5 launch profile
`standalone`	Website or LMS that hosts HTML ZIP without SCORM

Ask your LMS administrator if unsure. Start with SCORM 1.2 unless they specify otherwise.

Build commands¶

lxpack validate --target scorm12

lxpack validate --target scorm12
lxpack build --target scorm12

Output (default): .lxpack/<course-name>-scorm12.zip

Other targets:

lxpack build --target scorm2004

lxpack build --target scorm2004
lxpack build --target xapi
lxpack build --target cmi5
lxpack build --target standalone -o ./dist/standalone.zip

Unpacked folder instead of ZIP:

lxpack build --target standalone --dir -o ./dist/sta...

lxpack build --target standalone --dir -o ./dist/standalone

xAPI and cmi5 requirements¶

Add to course.yaml:

tracking:
  completion:
    threshold: 0.9
  xapi:
    activityIri: "https://training.example.com/courses/security-2026"
    displayName: Security 2026

activityIri must be a stable HTTPS URL your organization controls
Validate before build:

lxpack validate --target xapi

  lxpack validate --target xapi
  lxpack build --target xapi
  ```

Examples: `examples/xapi-awareness`, `examples/cmi5-demo`.

## Default target in config

`lxpack.config.json`:

```json
{
  "exports": {
    "defaultTarget": "scorm12"
  },
  "output": {
    "dir": ".lxpack"
  }
}

Then lxpack build without -t uses that default.

Handoff checklist for LMS admin¶

Provide:

ZIP from .lxpack/
Target type (SCORM 1.2 / 2004 / xAPI / cmi5)
Completion rule (tracking.completion.threshold)
Quiz pass scores (passingScore per assessment)
Staging test accounts and date tested

After upload¶

Launch as a learner — complete one lesson, one lab, one quiz
Confirm completion reports in LMS
For SCORM 2004, test resume (suspend data) if required
For xAPI, confirm statements in the LRS

SCORM 2004 table of contents order¶

Multi-SCO SCORM 2004 manifests list all lessons first, then all assessments in the LMS table of contents. That order may differ from how lessons appear in course.yaml when you interleave content with branching flow. Runtime navigation still follows flow inside the package; the LMS menu is a coarse outline.

SCORM 2004 completion status¶

When a learner finishes an attempt without passing, the runtime may set success_status to failed and completion_status to completed (the attempt is finished, not that the course objective is fully met). Validate rollup behavior in your LMS before production.

cmi5 `fetch` launch¶

cmi5 packages may include a fetch launch parameter. When present, the runtime POSTs to that URL (per the cmi5 spec) to obtain an auth-token for LRS requests. The launch URL must still include endpoint (and typically actor, registration). The token is cached in sessionStorage so a page refresh does not repeat the one-time fetch call. Use preview xAPI logging or your LMS staging environment to verify statements.

Troubleshooting LMS issues¶

Symptom	Check
Package won't import	Wrong SCORM version; try `scorm12`
Quiz always fails	`passingScore` and question keys
No completion	`tracking.completion.threshold` too high
xAPI silent	`activityIri`, LMS LRS config
Flow jump missing in SCORM 2004 SCO	Launch the correct activity; flow `goto` outside the current SCO is not applied

See Troubleshooting.