dependabot[bot] fede542084 chore(deps): bump actions/setup-node from 4.4.0 to 7.0.0 (#6)
Bumps [actions/setup-node](https://github.com/actions/setup-node) from 4.4.0 to 7.0.0.
- [Release notes](https://github.com/actions/setup-node/releases)
- [Commits](https://github.com/actions/setup-node/compare/49933ea5288caeca8642d1e84afbd3f7d6820020...820762786026740c76f36085b0efc47a31fe5020)

---
updated-dependencies:
- dependency-name: actions/setup-node
  dependency-version: 7.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2026-09-15 11:36:47 -04:00

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:

  1. Looks up the game's binding (no-op when unset).
  2. Validates the ROM exists through the scoped game:fs API.
  3. Probes configured emulators through the allowlisted system:command runner and drops anything missing or failing (--version probe).
  4. 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
S
Description
Emulator and ROM linking plugin for Drop
Readme
168 KiB
0 Stars 1 Watchers 0 Forks
2026-11-06 17:29:17 -10:00
Languages
TypeScript 76.9%
JavaScript 23.1%