`check` doesn't seem to generate the file bindings about cargo-component

[peterhuene]

It works here as I would expect and we have test coverage for the command.

To verify, what's the --version output of cargo-component and what version of cargo-component-bindings is being referenced in Cargo.toml for the project?

Was there a "Generating bindings for " message printed (should be the first one in the output, typically)?

This is the error I would expect if cargo-component-bindings was bumped to 0.4.0 but cargo-component itself remained at a previous version.

Additionally, if you set the CARGO_COMPONENT_LOG=debug environment variable, there should be some early log output from cargo-component regarding its decision to generate bindings and to where; that might shed light on why the bindings.rs file is missing.

[bnjbvr]

My bad, I got the error in a Github CI action and that was because the Rust cache action cached the .cargo/bin binaries, so I was using an old version. Clearing the cache fixed it 👍

[peterhuene]

The check command should be generating the file. Let me look into it.

[peterhuene]

Unrelated to the issue here, but the error coming from the macro should probably just be "did you forget to run cargo component <command>?" rather than assume the command was build. I'll fix that in the hopes that it reduces the confusion that build must be run.