Elite Dangerous Almanac / TypeScript

Static Elite Dangerous data and calculations for community applications and research — procedural system names and id64 addresses, galactic regions and nebulae, ships and outfitting with build metrics, personal equipment and engineering materials, localized display text, market commodities, and the galaxy map's location markers.

npm install @elite-dangerous-almanac/core

ESM-only, Node.js 22+ and modern browser bundlers, every module side-effect free.

import { ProceduralSystem } from '@elite-dangerous-almanac/core/astro/procedural-system';
import { BuildMetrics } from '@elite-dangerous-almanac/core/ships/build-metrics';
import { ShipLoadout } from '@elite-dangerous-almanac/core/ships/ship-loadout';
import type { LoadoutEvent } from '@elite-dangerous-almanac/core/ships/slef';

ProceduralSystem.fromName('Synuefe EN-H d11-96')?.systemAddress; // -> 3309179996515n

// One `Loadout` line from a player journal.
function jumpRangeOf(journalLine: string) {
    const event = JSON.parse(journalLine) as LoadoutEvent;
    return BuildMetrics.of(ShipLoadout.fromLoadout(event)).maxJumpRange(); // -> 60.5478
}

• Getting started — install, which import to use, and the symbol-to-subpath map.
• Reading a player journal — turning Loadout and FSDJump events into library objects.
• Building an outfitting screen — mounts, what fits, fitting it, and every metric a shipyard shows.
• Build metrics — how power, shields, armour, weapons, ammunition and range are computed.
• Engineering — what a recipe may go on, what it rolls, and what a roll costs.
• Working with SLEF — reading and writing loadout exports, and retail against captured credits.
• Systems and regions — the id64 round trip, both coordinate spaces, and the four meanings of "region".
• The failure model — null against the three errors, and diagnostic results for unavailable metrics.

The bulk data catalogues live on their own subpaths and are listed in full on the API reference.

Browse the complete API reference — every module, class, function and type, generated from the source documentation.

The same data and the same behaviour are published as a .NET package, with guides, a reference and navigation of its own: the .NET wiki. The names differ — each package is written the way its own language reads — but the behaviour does not, and the fixtures under fixtures/ prove it for both.

The bundled game and community data has source-specific licensing, including non-commercial terms. Review LICENSE and ATTRIBUTIONS.md before redistribution or commercial use.