---
title: "Studiolxd Scorm"
description: "This is a content-side wrapper: the thing your course imports so it can talk to whatever LMS launched it. A framework-agnostic core locates the API object by walking window.parent and opener, then exposes one typed session over either SCORM 1.2 or SCORM 2004, with thin adapters for React, Vue, Angular, Svelte, Web Components and a plain <script> global."
canonical_url: "https://scorm-tools.com/tools/studiolxd-scorm"
last_updated: "2026-10-31T10:21:59.644Z"
---

This is a content-side wrapper: the thing your course imports so it can talk to whatever LMS launched it. A framework-agnostic core locates the API object by walking `window.parent` and `opener`, then exposes one typed session over either SCORM 1.2 or SCORM 2004, with thin adapters for React, Vue, Angular, Svelte, Web Components and a plain `<script>` global.

The useful part is the abstraction over the two data models. Calls such as `setComplete()`, `setScore()` and `setExit('suspend')` map to `cmi.core.lesson_status` under 1.2 and `cmi.completion_status` / `cmi.success_status` under 2004, so a course written once can be exported for either. Typed CMI path builders and mock drivers mean the whole integration can be developed and unit-tested without an LMS, and the repository carries a real test suite covering both drivers and every adapter.

What it is not: an LMS-side implementation, a packager, or a manifest generator. It will not build you a zip, and there is no xAPI or cmi5 path — this is SCORM only.

Judgement for someone choosing today: the code is careful and the API surface is well documented in six languages, but this is a new project by one studio, first published in February 2026, renamed from `@studiolxd/react-scorm` at v2.0.0 and carrying no community yet. The MIT licence file sits inside `packages/scorm`, not the repository root, so GitHub reports the repo as unlicensed. Reasonable to adopt if you are prepared to read the source; too young to treat as infrastructure.