Using cargo-bavy it generates this:

["profile.dev"]
opt-level = 1

["profile.dev.package.\"*\""]
opt-level = 3

Which produces the following warnings:

warning: unused manifest key: profile.dev
warning: unused manifest key: profile.dev.package."*"

It should be:

[profile.dev]
opt-level = 1

[profile.dev.package."*"]
opt-level = 3

Creating a project with nightly toolchain disabled and fast linker enabled causes this error when running the project:

error: the option `Z` is only accepted on the nightly compiler

If the nightly toolchain is not selected, rustflags = ["-Zshare-generics=n"] should not be added to the .cargo/config.toml file as it is a nightly only feature.

P.S. I was just thinking the other night about making something like this, thanks for making it!

When using the optimized dependency configuration, you get the following warnings when running cargo check:

warning: unused manifest key: profile.dev
warning: unused manifest key: profile.dev.package."*"

This seems to be because profile.dev and profile.dev.package."*" are quoted and apparently cargo can't handle that.

We need to find a way to insert those tables without being quoted, unfortunately the documentation is quite sparse here.

Closes #19.

cargo bavy new now provides an option to configure Rust Analyzer in VS Code to use the bevy/dynamic feature.

This reduces compile times and avoids unnecessary re-compilations when you use cargo bavy commands. It should be enabled on all projects where you use cargo bavy.

If you use cargo bavy run, it automatically passes --features bevy/dynamic for faster compiles. However, Rust Analyzer doesn't use this feature, so it re-compiles Bevy from scratch every time.

cargo bavy new should automatically create a .vscode/settings.json file (if this is selected by the user), with the following content:

{
  "rust-analyzer.cargo.features": ["bevy/dynamic"]
}

This way, Rust Analyzer uses the same features as the user, so every compile remains fast.

Closes #14.

cargo bavy new will now automatically install missing WASM tools if the WASM option has been selected.

The cargo bavy new output is now also colorized and suggests using cargo bavy run instead of cargo run.

Fixes #15.

This properly passes the GitHub token to the Clippy CI workflow. This allows the workflow to comment Clippy warnings on your PRs.

I previously thought the token wasn't needed, but it was.

Closes #6.

Adds a new cargo bavy check command that works similar to its cargo counterpart, but automatically passes --features bevy/dynamic in debug mode, for faster compile times. It also has a --wasm flag to quickly check for the web.

I removed a GitHub token reference from the CI workflow, thinking that it was useless. However, it allows the workflow to automatically comment clippy issues on PRs, so it should be added back.

Closes #7.

• Added cargo bavy build command. It works similar to its cargo counterpart, but automatically passes --features bevy/dynamic in debug builds for faster compile times. It also includes a --wasm/-w flag to bundle a binary for the web.
• Refactored ArgBuilder to be a lot less verbose to use.

Fixes #10.

There was one shared generic flag left in the linker configuration with stable toolchain, this has now been fixed to only be included on nightly Rust.

Just like with cargo new, you should be able to pass a --lib flag to create a library instead of a binary project. The feature selection should be adapted to make sense for libraries.

Currently, the program just panics with an error message when something goes wrong. Ideally, we'd have better and prettier errors that are more helpful to the user.