bin/node/cli/src/cli.rs looks like a regular module. But if you for example try to reference a sibling module from it, the compiler will confusingly tell you that this sibling module can't be found. This is because as well as being built as a regular module, cli.rs is also included in build.rs. AFAICT this is to generate shell completions at build time. It seems like this could be achieved without using include!. The simplest option might be to have a separate crate just for generating shell completions. This could pull in cli.rs via a crate dependency.
bin/node/cli/src/cli.rslooks like a regular module. But if you for example try to reference a sibling module from it, the compiler will confusingly tell you that this sibling module can't be found. This is because as well as being built as a regular module,cli.rsis also included inbuild.rs. AFAICT this is to generate shell completions at build time. It seems like this could be achieved without usinginclude!. The simplest option might be to have a separate crate just for generating shell completions. This could pull incli.rsvia a crate dependency.