enable bevy_dev_tools by default

[mockersf]

Objective

• Default features are mostly useful to new users of Bevy, or when running examples in the repo
• Those two cases are mostly developers, but they need to take an extra step to enable bevy_dev_tools

Solution

• Enable bevy_dev_tools by default

[afonsolage]

I agree, but if this is the case, the docs also needs to be updated:

bevy/crates/bevy_dev_tools/src/lib.rs

Lines 26 to 52 in eac8bc7

	/// Enables developer tools in an [`App`]. This plugin is added automatically with `bevy_dev_tools`
	/// feature.
	///
	/// Warning: It is not recommended to enable this in final shipped games or applications.
	/// Dev tools provide a high level of access to the internals of your application,
	/// and may interfere with ordinary use and gameplay.
	///
	/// To enable developer tools, you can either:
	///
	/// - Create a custom crate feature (e.g "`dev_mode`"), which enables the `bevy_dev_tools` feature
	/// along with any other development tools you might be using:
	///
	/// ```toml
	/// [feature]
	/// dev_mode = ["bevy/bevy_dev_tools", "other_dev_tools"]
	/// ```
	///
	/// - Use `--feature bevy/bevy_dev_tools` flag when using the `cargo run` command:
	///
	/// `cargo run --features bevy/bevy_dev_tools`
	///
	/// - Add the `bevy_dev_tools` feature to the bevy dependency in your `Cargo.toml` file:
	///
	/// `features = ["bevy_dev_tools"]`
	///
	/// Note: The third method is not recommended, as it requires you to remove the feature before
	/// creating a build for release to the public.

[alice-i-cecile]

I agree that we should do this :)

[cart]

I'm of the mind that this is better suited to some "dev" cargo feature (which we've discussed in the past), which would enable a common collection of features useful for development: tracing, dev tools, asset hot reloading, embedded hot reloading, etc

[cart]

In general I think we should consider moving in the direction of a smaller baseline feature set with larger "meta" features that pull in targeted collections of cargo features (ex: "3d", "2d", "dev", etc). I consider --no-default-features to be a non-viable lifestyle for people actually building apps.

[cart]

#21472 will resolve this in a more complete way, so I'm closing this

[cart]

It does not resolve the "add dev tools by default to examples" issue. But I am of the mind that Bevy's default feature set should not be a dumping ground for whatever our examples happen to need. The default feature set is "the complete shippable bevy experience". Dev tools should not be shipped with bevy apps by default.