Skip to content

Conversation

@sameerthawait
Copy link

Summary

Fixes a Windows-specific issue where prepare-sidecar.mjs exited early
during Tauri beforeDevCommand, causing sidecar initialization to be
incomplete.

Root Cause

On Windows, calling process.exit(0) inside beforeDevCommand can cause
Tauri to treat the command as failed, preventing the sidecar from being
ready on first launch.

Fix

Removed the early process.exit(0) and allowed the script to complete
naturally, ensuring proper sidecar setup.

Verification

  • prepare-sidecar.mjs completes successfully on Windows
  • beforeDevCommand no longer fails
  • Sidecar is correctly detected on first launch

Fixes #270

@github-actions
Copy link
Contributor

The following comment was made by an LLM, it may be inaccurate:

@sameerthawait
Copy link
Author

Thanks! Happy to make any changes if needed.

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.

Windows: sidecar engine fails to connect on first launch

1 participant