openspace-api-js

TypeScript/JavaScript library for interfacing with OpenSpace via TCP sockets and WebSockets.

Installation

npm

If you are using npm, install the latest version:

npm install openspace-api-js

Script tag

If you are including the API via a script tag, the preferred approach is to load it directly from the OpenSpace CDN:

<scripttype="text/javascript" src="https://liu-se.cdn.openspaceproject.com/api/1.0.0/openspace-api.js"></script>

If you require an offline-capable version, download the latest release and serve it locally:

<scripttype="text/javascript" src="openspace-api.js"></script>

Migration

If you are upgrading from a previous version of this library, please see the migration guide.

Usage

The TypeScript/JavaScript API can be used in both Node.js setups as well as browser-based setups.

Node.js (TCP socket)

Connects to OpenSpace on port 4681 by default.

TypeScript example and JavaScript example provide examples of how to connect from a Node.js application. To run the bundled Node.js example:

npm install
npm run examples-typescript # TypeScript
npm run examples-javascript # JavaScript

Browser (WebSocket)

Connects to OpenSpace on port 4682 by default.

If you are loading the library as a plain <script> tag (e.g. openspace-api.js from the CDN or a downloaded bundle), the factory function is exposed on window:

<scriptsrc="openspace-api.js"></script><script>constapi=window.openspaceApi('localhost',4682);api.onConnect(async()=>{constopenspace=awaitapi.library();consttime=awaitopenspace.time.UTC();console.log('Simulation time:',time);});api.connect();</script>

See HTML example for a complete working example. For simplicity, it is self-contained in the index.html file.

If you are importing the library as an ES module from an npm-based project, import the entry point directly:

importopenspaceApifrom'openspace-api-js';constapi=openspaceApi('localhost',4682);

Generating types from your OpenSpace build

The package ships with pre-generated types targeting a specific OpenSpace version. If your build differs, you can regenerate them locally. There are two separate generators, one for topic types and one for the Lua library. Both write directly into src/types/generated/.

Topic types (generate-topic-types)

Reads JSON schema files from OpenSpace's support/types/ directory and compiles them to TypeScript using json-schema-to-typescript.

Prerequisites:

• Node.js
• OpenSpace version 0.22 or later

Steps:

1. Run OpenSpace DocsWriter.exe
2. Locate the support/types/ directory in your OpenSpace source tree
3. Run:

npm run generate-topic-types -- "<path-to-openspace>/support/types"

This writes the generated files into src/types/generated/ and rebuilds the AllTopics union type used throughout the API.

Lua library types (generate-lua-library)

Connects to a running OpenSpace instance, fetches the full Lua API documentation via the documentation topic, and generates src/types/generated/openspacelualibrary.ts.

Why generate this instead of publishing it once? The OpenSpace Lua API changes frequently, so these types are generated from a live instance rather than published to @types or DefinitelyTyped. Keeping generation in this repo means changes can be reflected immediately without going through an external approval process.

Prerequisites:

• Python >= 3.12
• The OpenSpace Python API must be installed and importable
• OpenSpace must be running and reachable on localhost:4681

Steps:

1. Start OpenSpace.
2. Run:

npm run generate-lua-library

This installs the Python dependencies (via pip install -r script/requirements.txt) and runs script/generatetypescriptfile.py, writing the result to src/types/generated/openspacelualibrary.ts.

Note: The generated file is specific to the OpenSpace version that was running when the script executed. Type hints may be inaccurate if your runtime version differs from the version used to generate them.