Fix windows dev setup#2182
Merged
rafaellehmkuhl merged 2 commits intobluerobotics:masterfrom Oct 12, 2025
Merged
Conversation
rafaellehmkuhl
approved these changes
Oct 12, 2025
Member
rafaellehmkuhl
left a comment
There was a problem hiding this comment.
Just tested on macOS and it's working perfectly as well. Thanks Bob!
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This makes
yarn dev:electronwork on all platforms. Windows has a different syntax for setting temporary env variables before launch. Adding the cross-env fixes that.I also added this to "build:lib". Not entirely sure what that one does yet, but it was really the only other candidate for cross-env. The deploy scripts all rely on
sed, so they aren't going to work on Windows anyway, so I didn't bother. Those aren't really needed locally, and if I ever did (for some reason), I'd just use WSL.