Skip to content

Fix wavedash dev for Ruffle and JsDos engines#25

Draft
cloud9c wants to merge 1 commit intomainfrom
fix/ruffle-dev-entrypoint
Draft

Fix wavedash dev for Ruffle and JsDos engines#25
cloud9c wants to merge 1 commit intomainfrom
fix/ruffle-dev-entrypoint

Conversation

@cloud9c
Copy link
Contributor

@cloud9c cloud9c commented Mar 24, 2026

Summary

  • wavedash dev failed with "Engine config requires an entrypoint" for Ruffle and JsDos projects
  • Root cause: the dev command called entrypoint() for all three engine types (Custom, JsDos, Ruffle), but entrypoint() only reads from [custom].entrypoint
  • Fix: only require entrypoint() for Custom engines; for Ruffle/JsDos, pass executable_entrypoint_params() instead — matching the existing build push logic

Test plan

  • Run wavedash dev from a project with a [ruffle] config — should launch dev server without error
  • Run wavedash dev from a project with a [jsdos] config — should work similarly
  • Run wavedash dev from a project with a [custom] config — should still require entrypoint as before

🤖 Generated with Claude Code

The dev command incorrectly required `entrypoint()` (which only reads
from [custom].entrypoint) for Ruffle and JsDos engines. This caused
"Engine config requires an entrypoint" errors for valid Ruffle/JsDos
configs. Now mirrors the build push logic: Custom uses entrypoint(),
Ruffle/JsDos use executable_entrypoint_params().

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant