Files
horizon-airdef/website/package.json
T
Ludovic Marie fde383c6e8 Website: read 0.2 tags (v0.2.0, launcher@0.2.0) as newer than the dated ones
From 0.2 the game is tagged vX.Y.Z and the launcher launcher@X.Y.Z (docs/versioning.md). The site
took only vYYYY.MM.DD as a game release and launcher-v as a launcher, so it would keep offering
launcher 0.16 and showing the last dated patch notes.

src/versions.js holds the tag test and order (every 0.2 tag above every tag from before, semver
within, a pre-release before its release), shared by build.mjs and main.js; the download button
picks the newest launcher by tag, the notes the newest stable game releases, and the launcher
lookup falls back to launcher@ tags before launcher-v. Nothing shows "0.2" until a 0.2 release
exists. `npm test` runs its tests (node --test).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-22 02:13:33 +02:00

20 lines
494 B
JSON

{
"name": "horizon-website",
"private": true,
"type": "module",
"description": "horizon's website: a static page in the launcher's design",
"scripts": {
"build": "node build.mjs",
"start": "node serve.mjs",
"dev": "node build.mjs && node serve.mjs",
"assets": "node scripts/assets.mjs",
"shots": "node scripts/shots.mjs",
"test": "node --test src/"
},
"devDependencies": {
"sharp": "^0.34.4",
"wawoff2": "^2.0.1",
"playwright": "^1.56.0"
}
}