-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bevy build #102
Bevy build #102
Conversation
In general, this change looks good! I love how easy I have a few comments and there are some merge conflicts, but then it's good to go! |
@@ -1,3 +1,4 @@ | |||
#![expect(dead_code, reason = "Will be used for bevy bump and perhaps bevy run")] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure why this lint wasn't emitted before...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! Merge it when you feel like it's ready :)
This PR adds the remaining pieces needed for the
bevy build
command.The command is a wrapper around
cargo build
, but with an additionalweb
sub command which makes it a lot easier to build an app for the browser.I also plan to add additional features in the feature, like #68.
The PR contains the following changes:
cargo install
wrapper to install a program if it's missing (prompting the user).Cargo.toml
. There are likely better ways to do this (perhaps viacargo metadata
), but I already had this implemented and we can improve it in a follow-up if needed.If you'd prefer smaller PRs let me know and I will split this up further.