Using css-modules crate results in macro-error but compiles and works.

Example

src/app.css

.something {
   background: red
}

src/main.rs

use css_modules::include_css_module;

fn main() {
  let css = include_css_module!("app.css");
  println!("{}", css["something"]);
}

./build.rs :

use css_modules::CssModules;

fn main() {
    let mut css_modules = CssModules::default();

    // Include all CSS files in the src dir:
    css_modules.add_modules("src/**/*.css").unwrap();

    // Compile all modules and export CSS into one file:
    css_modules.compile("./app.css");
}

./Cargo.toml

# ...
[dependencies]
css-modules = "0.5"
[build-dependencies]
css-modules = "0.5"

Error

message: called `Result::unwrap()` on an `Err` value: StripPrefixError(())

Maybe Rust-analyzer does not find the file that Rust does.

Reproduce the macro error using the provided src/app.css, src/main.rs, build.rs, and Cargo.toml example, comparing rust-analyzer's result with the successful Rust build. Start by tracing how the include_css_module! call resolves app.css and handles the build-script output. Done means the example no longer reports a macro error while retaining its existing compiled behavior.