0 Fork 0

mirror of https://github.com/Heretek-Games/drop-emulation.git synced 2026-11-07 10:05:59 -10:00

T

BillyOutlast 35833a7af3 ci: add a shared ESLint flat-config lint gate

Add eslint.config.mjs (eslint:recommended + typescript-eslint recommended,
type-unaware) with a `lint` script and a CI step. Rules that need a baseline
cleanup pass (no-explicit-any, ban-ts-comment, no-useless-assignment,
preserve-caught-error) are warnings; core rules and unused vars are errors.

Refs Heretek-Games/drop#69 (audit finding F-23).

2026-09-14 19:59:21 -04:00

.github

ci: add a shared ESLint flat-config lint gate

2026-09-14 19:59:21 -04:00

src

fix(ci): harden npm install and drop unused import

2026-09-14 09:10:12 -04:00

test

feat(launch): rewrite ROM launch command with validated bindings

2026-09-14 09:02:13 -04:00

.gitignore

feat(init): scaffold drop-emulation (plugin API v2)

2026-09-14 01:24:26 -04:00

AGENTS.md

chore: resolve plugin SDK from registry and add typecheck/CI

2026-09-14 09:02:13 -04:00

CLAUDE.md

feat(init): scaffold drop-emulation (plugin API v2)

2026-09-14 01:24:26 -04:00

drop-plugin.json

feat(launch): rewrite ROM launch command with validated bindings

2026-09-14 09:02:13 -04:00

eslint.config.mjs

ci: add a shared ESLint flat-config lint gate

2026-09-14 19:59:21 -04:00

GEMINI.md

feat(init): scaffold drop-emulation (plugin API v2)

2026-09-14 01:24:26 -04:00

package-lock.json

ci: add a shared ESLint flat-config lint gate

2026-09-14 19:59:21 -04:00

package.json

ci: add a shared ESLint flat-config lint gate

2026-09-14 19:59:21 -04:00

README.md

chore: resolve plugin SDK from registry and add typecheck/CI

2026-09-14 09:02:13 -04:00

SECURITY.md

chore: add SECURITY.md and Dependabot config

2026-09-14 19:35:48 -04:00

tsconfig.json

feat(init): scaffold drop-emulation (plugin API v2)

2026-09-14 01:24:26 -04:00

README.md

Drop Emulation

Emulator and ROM linking plugin for Drop (#10, #189).

How it works

Per-game bindings are stored under the client storage key binding:<gameId> as { emulatorId, coreId, romPath, command? }. Emulator definitions live under the emulators key (falling back to the built-in list in src/emulator.ts).

During the pre-launch:prepare stage the plugin:

Looks up the game's binding (no-op when unset).
Validates the ROM exists through the scoped game:fs API.
Probes configured emulators through the allowlisted system:command runner and drops anything missing or failing (--version probe).
Rewrites the launch command, expanding {core} and {rom_path} in the template, and publishes metadata.launchCommand plus metadata.emulation on the launch context.

A game-detail:panels slot (EmulatorPanel) shows the configured binding.

Build

npm ci
npm run build
npm test
npm run typecheck