Errors when re-exporting bevy | Bevy | Page 1

hexed vessel Dec 21, 2025, 1:29 PM

#

I'm currently refactoring my code into separate crates and I've created a core crate that re-exports bevy, so all my crates use the same bevy version and I only need to change it in core if I decide to upgrade to a new version.

but doing this gives me the following error in the ide:
failed to resolve: use of unresolved module or unlinked crate 'bevy_ecs'

example code:

use spirit_hotel_core::bevy::prelude::*;

#[derive(Component, Default, Debug, Reflect)]
#[reflect(Component, Default)]
pub struct CanPush;

strong geyser Dec 21, 2025, 7:32 PM

#

This may be a bug in bevy. It's probably worth filing a bug.

However, a different solution is to just use workspace dependencies. In your workspace Cargo.toml, you add a [workspace.dependencies] section, specify your dependencies, and then in your crate files, you specify your dependency like bevy = { workspace = true }

hexed vessel Dec 22, 2025, 12:28 PM

#

strong geyser This may be a bug in bevy. It's probably worth filing a bug. However, a differ...

I need the sub crates to be local right?
or can I use github references for the crates and reference the crates as members of the workspace?

crisp pulsar Dec 22, 2025, 2:41 PM

#

[workspace.dependecies] works the same as the normal packages [dependencies], so crates.io, git or local works fine

hexed vessel Dec 22, 2025, 2:42 PM

#

but then what do I write into the members section, or is that optional?

crisp pulsar Dec 22, 2025, 2:42 PM

#

what is the structure of you project? how many Cargo.toml and their locations

hexed vessel Dec 22, 2025, 2:49 PM

#

crisp pulsar what is the structure of you project? how many `Cargo.toml` and their locations

game
 - crates/
  - game_core
  ... (23 crates in total)
 - src/
 - cargo.toml (workspace root)

#

game/cargo.toml:

[workspace]
members = ["crates/game*"]

[workspace.dependencies]
...

crisp pulsar Dec 22, 2025, 2:50 PM

#

the main app (workspace root) depends on all of the subcrates, right?

hexed vessel Dec 22, 2025, 2:50 PM

#

yes

crisp pulsar Dec 22, 2025, 2:52 PM

#

e.g.,

[workspace]
members = ["crates/*"]

[package]
name = "spirit_hotel"

[workspace.dependecies]
bevy = "0.17.3"
game_core = { path = "crates/game_core" }
other23crates = { path = "..." }

[dependencies]
bevy = { workspace = true }
game_core = { workspace = true }
other23crates = { workspace = true }

#

and on each of the subcrates you would also be able to use bevy = { workspace = true}

hexed vessel Dec 22, 2025, 2:54 PM

#

but if I used github links instead of placing all my crates into "crates/..." then the crates folder would be empty and I wouldn't have a way to tell the workspace root that the github packages are members of the workspace

crisp pulsar Dec 22, 2025, 2:56 PM

#

then it would be

[package]
name = "spirit_hotel"

[workspace.dependecies]
bevy = "0.17.3"
game_core = { git = "https://github.com/???/game_core" }
other23crates = { git = "..." }

[dependencies]
bevy = { workspace = true }
game_core = { workspace = true }
other23crates = { workspace = true }

hexed vessel Dec 22, 2025, 2:57 PM

#

and game_core would automatically know that it is part of the game workspace?

crisp pulsar Dec 22, 2025, 2:57 PM

#

wait, then you project would only have 1 crate on it, all of the workspace members on crates/... will have their own git repo?

hexed vessel Dec 22, 2025, 2:57 PM

#

yes

crisp pulsar Dec 22, 2025, 2:57 PM

#

[package]
name = "spirit_hotel"

[dependencies]
bevy = "0.17.3"
game_core = { git = "https://github.com/???/game_core" }
other23crates = { git = "..." }

#

and each of the other crates would have their dependencies linking to the other repos

hexed vessel Dec 22, 2025, 2:59 PM

#

but I want to still be able to do bevy = { workspace = true } in each github repo

crisp pulsar Dec 22, 2025, 2:59 PM

#

workspace is only if you have Cargo.toml under another in the file hierarchy

hexed vessel Dec 22, 2025, 3:01 PM

#

so either I wait for a fix from the bevy team or I have all crates in one github repo/file hierarchy with a workspace

crisp pulsar Dec 22, 2025, 3:02 PM

#

yes

#

having on the same workspace is best, unless you are creating something that you intend on using on multiple projects

#

and even then you could still do

[package]
name = "spirit_hotel_2"

[dependencies]
game_core = { git = "https://github.com/???/spirit_hotel" }

hexed vessel Dec 22, 2025, 3:07 PM

#

oki

#Errors when re-exporting bevy